Github user kkhatua commented on the issue:
https://github.com/apache/drill/pull/1159
@kfaraaz Are there unit tests specific to the JDBC Storage Plugin? They're
not the same as the JDBC unit tests, which test the Drill JDBC driver.
While the change seems straightforward, I'm not sure if all JDBC drivers
support PreparedStatement. For e.g., within Drill, the PreparedStatement is
executed as a standard Statement object, which is why this _works_ functionally.
What happens if a JDBC driver backing the JDBC storage plugin does not
support PreparedStatement (i.e. it is a No-Op)?
---
