[HIVE-5232] Make JDBC use the new HiveServer2 async execution API by default

• Type: Sub-task
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 0.13.0
• Fix Version/s: 0.13.0
• Component/s: HiveServer2
• Assignee: Vaibhav Gumashta
• Reporter: Vaibhav Gumashta
• Created: 05/Sep/13 21:42
• Updated: 03/Mar/14 10:56
• Resolved: 03/Mar/14 10:56

Description

HIVE-4617 provides support for async execution in HS2. There are some proposed improvements in followup JIRAs:
HIVE-5217
HIVE-5229
HIVE-5230
HIVE-5441

There is also HIVE-5060 which assumes that execute to be asynchronous by default.

Once they are in, we can think of using the async API as the default for JDBC. This can enable the server to report back error sooner to the client. It can also be useful in cases where a statement.cancel is done in a different thread - the original thread will now be able to detect the cancel, as opposed to the use of the blocking execute calls, in which statement.cancel will be a no-op.

Issue Links

• blocks: HIVE-6472 JDBC cancel will not work with current HiveServer2
• is blocked by: HIVE-5217 Add long polling to asynchronous execution in HiveServer2
• is blocked by: HIVE-5229 Better thread management for HiveServer2 async threads
• is blocked by: HIVE-5230 Better error reporting by async threads in HiveServer2
• is blocked by: HIVE-5441 Async query execution doesn't return resultset status
• is blocked by: HIVE-5060 JDBC driver assumes executeStatement is synchronous
• is blocked by: HIVE-4617 Asynchronous execution in HiveServer2 to run a query in non-blocking mode
• relates to: HIVE-6535 JDBC: provide an async API to execute query and fetch results