[
https://issues.apache.org/jira/browse/HIVE-6535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vaibhav Gumashta updated HIVE-6535:
-----------------------------------
Resolution: Fixed
Hadoop Flags: Reviewed
Fix Version/s: 2.1.0
Release Note:
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.
Target Version/s: 2.1.0
Status: Resolved (was: Patch Available)
Committed to master. Thanks [~thejas] for reviewing.
> JDBC: provide an async API to execute query and fetch results
> -------------------------------------------------------------
>
> Key: HIVE-6535
> URL: https://issues.apache.org/jira/browse/HIVE-6535
> Project: Hive
> Issue Type: Improvement
> Components: HiveServer2, JDBC
> Affects Versions: 0.14.0, 1.2.1, 2.0.0
> Reporter: Thejas M Nair
> Assignee: Vaibhav Gumashta
> Fix For: 2.1.0
>
> Attachments: HIVE-6535.1.patch, HIVE-6535.2.patch, HIVE-6535.3.patch,
> HIVE-6535.4.patch, HIVE-6535.5.patch, HIVE-6535.6.patch
>
>
> 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.
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
