[HIVE-6535] JDBC: provide an async API to execute query and fetch results

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 0.14.0, 1.2.1, 2.0.0
• Fix Version/s: 2.1.0
• Component/s: HiveServer2, JDBC
• Target Version/s: 2.1.0
• Hadoop Flags: Reviewed

Release Note

Introduced new method HiveStatement.executeAsync - Starts the query execution asynchronously on the server, and immediately returns to the client. The client subsequently blocks on ResultSet#next or Statement#getUpdateCount, depending on the query type. Users should call ResultSet.next or Statement#getUpdateCount (depending on whether query returns results) to ensure that query completes successfully. Calling another execute method, or close before query completion would result in the async query getting killed if it is not already finished.
Note: This method is an API for limited usage outside of Hive by applications like Apache Ambari, although it is not part of the interface java.sql.Statement.

• Assignee: Vaibhav Gumashta
• Reporter: Thejas Nair
• Created: 03/Mar/14 10:54
• Updated: 27/Feb/17 04:03
• Resolved: 15/Apr/16 22:33

Description

The hive jdbc client waits query completion during execute() call. It would be better to block in the jdbc for completion when the results are being fetched.
This way the application using hive jdbc driver can do other tasks while asynchronous query execution is happening, until it needs to fetch the result set.

Issue Links

• is related to: HIVE-5232 Make JDBC use the new HiveServer2 async execution API by default
• is related to: AMBARI-16963 Hive View: Should use hive jdbc to connect to hiveserver2
• is related to: HIVE-5571 Add support for COMPILING state to OperationState in HiveServer2
• links to: Review Board