Due to irods/irods#3902 and first reported in #281. In 5.0.0, this issue is resolved with no additional changes due to the updated GenQuery1 parser.
For 4.3, we can try replacing all the queries with GenQuery2, but this might break existing deployments using GenQuery1-based custom violating queries. This would resolve the problem, so, might be worth the upgrade trouble.
Due to irods/irods#3902 and first reported in #281. In 5.0.0, this issue is resolved with no additional changes due to the updated GenQuery1 parser.
For 4.3, we can try replacing all the queries with GenQuery2, but this might break existing deployments using GenQuery1-based custom violating queries. This would resolve the problem, so, might be worth the upgrade trouble.