[DRILL-2472] JDBC : ResultSet.wasNull should give proper error message when a user tries to call it before calling getXXX method

• Type: Bug
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Fix Version/s: 1.4.0
• Component/s: Client - JDBC
• Assignee: Unassigned
• Reporter: Rahul Kumar Challapalli
• Created: 16/Mar/15 00:21
• Updated: 28/Jan/16 21:19
• Resolved: 28/Jan/16 21:19

Description

git.commit.id.abbrev=7b4c887

Drill currently throws the below error when we call wasNull before calling getXXX method

Exception in thread "main" 17:15:07.935 [Client-1] DEBUG o.a.drill.exec.rpc.user.UserClient - Sending response with Sender 557575560
java.lang.ArrayIndexOutOfBoundsException: 1
	at org.apache.drill.jdbc.DrillAccessorList.wasNull(DrillAccessorList.java:53)
	at org.apache.drill.jdbc.DrillCursor.wasNull(DrillCursor.java:138)
	at net.hydromatic.avatica.AvaticaResultSet.wasNull(AvaticaResultSet.java:201)

Drill should instead give the appropriate error message

Issue Links

• Is contained by: DRILL-1735 JDBC driver's close() leaks resources in local mode
• relates to: DRILL-2463 Implement JDBC mapping of SQL NULL for ResultSet.getXxx() methods
• relates to: DRILL-2489 Accessing Connection, Statement, PreparedStatement after they are closed should throw a SQLException
• requires: DRILL-2769 many(?) JDBC methods throw non-SQLException exceptions (e.g., UnsupportedOperationException, RuntimeException)