Can you point me to the relevant PR which fixes this? Another user has reported a similar issue here. I feel best solution would be to upgrade, I want to ensure that their queries would need minimum changes once they go from v1.1.1 to v20.3 before I suggest the switch.