For anyone who may come across this thread in the future, we identified the issue as being caused by a bug in the conversion of queries to prepared statements. By disabling this conversion on the resource, we were able to get the queries to run. I have filed a bug report on this issue, and will update this thread when a fix had been implemented!