[DRILL-2489] Accessing Connection, Statement, PreparedStatement after they are closed should throw a SQLException

• Type: Bug
• Status: Reviewable
• Priority: Major
• Resolution: Unresolved
• Fix Version/s: Future
• Component/s: Client - JDBC
• Assignee: Unassigned
• Reporter: Rahul Kumar Challapalli
• Created: 17/Mar/15 23:35
• Updated: 12/Feb/23 21:05

Description

git.commit.id.abbrev=7b4c887

According to JDBC spec we should throw a SQLException when we access methods on a closed Connection, Statement, or PreparedStatement. Drill is currently not doing it.

I can raise multiple JIRA's if the developer wishes to work on them independently

Issue Links

• is related to: DRILL-2472 JDBC : ResultSet.wasNull should give proper error message when a user tries to call it before calling getXXX method
• is required by: DRILL-2769 many(?) JDBC methods throw non-SQLException exceptions (e.g., UnsupportedOperationException, RuntimeException)
• requires: DRILL-3347 Resolve: ResultSet.getObject(...) for VARCHAR returns ...hadoop.io.Text, not String
• requires: DRILL-3661 Add/edit various JDBC Javadoc.
• requires: DRILL-3566 Calling Connection.prepareStatement throws a ClassCastException
• links to: https://reviews.apache.org/r/37685