[
https://issues.apache.org/jira/browse/HIVE-5232?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vaibhav Gumashta updated HIVE-5232:
-----------------------------------
Description:
[HIVE-4617|https://issues.apache.org/jira/browse/HIVE-4617] provides support
for async execution in HS2. There are some proposed improvements in followup
JIRAs:
# [HIVE-5217|https://issues.apache.org/jira/browse/HIVE-5217]
# [HIVE-5229|https://issues.apache.org/jira/browse/HIVE-5229]
# [HIVE-5230|https://issues.apache.org/jira/browse/HIVE-5230]
# [HIVE-5441|https://issues.apache.org/jira/browse/HIVE-5441]
There is also [HIVE-5060|https://issues.apache.org/jira/browse/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.
was:
[HIVE-4617|https://issues.apache.org/jira/browse/HIVE-4617] provides support
for async execution in HS2. There are some proposed improvements in followup
JIRAs:
# [HIVE-5217|https://issues.apache.org/jira/browse/HIVE-5217]
# [HIVE-5229|https://issues.apache.org/jira/browse/HIVE-5229]
# [HIVE-5230|https://issues.apache.org/jira/browse/HIVE-5230]
# [HIVE-5441|https://issues.apache.org/jira/browse/HIVE-5441]
There is also [HIVE-5060|https://issues.apache.org/jira/browse/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 in a different thread and the
original thread will now be able to detect that.
> Make JDBC use the new HiveServer2 async execution API by default
> ----------------------------------------------------------------
>
> Key: HIVE-5232
> URL: https://issues.apache.org/jira/browse/HIVE-5232
> Project: Hive
> Issue Type: Sub-task
> Components: HiveServer2
> Affects Versions: 0.13.0
> Reporter: Vaibhav Gumashta
> Assignee: Vaibhav Gumashta
> Fix For: 0.13.0
>
> Attachments: HIVE-5232.1.patch, HIVE-5232.2.patch
>
>
> [HIVE-4617|https://issues.apache.org/jira/browse/HIVE-4617] provides support
> for async execution in HS2. There are some proposed improvements in followup
> JIRAs:
> # [HIVE-5217|https://issues.apache.org/jira/browse/HIVE-5217]
> # [HIVE-5229|https://issues.apache.org/jira/browse/HIVE-5229]
> # [HIVE-5230|https://issues.apache.org/jira/browse/HIVE-5230]
> # [HIVE-5441|https://issues.apache.org/jira/browse/HIVE-5441]
> There is also [HIVE-5060|https://issues.apache.org/jira/browse/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.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
