[
https://issues.apache.org/jira/browse/HIVE-4617?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13756340#comment-13756340
]
Thejas M Nair commented on HIVE-4617:
-------------------------------------
bq. Our of curiosity what would be the use case for async hive queries?
The primary motivation is not enabling one to submit many queries in parallel,
that can be also be done using existing API and multiple threads in the client
side.
The execute function in HS2 thrift api returns a operation handle. This
operation handle is then used to query for state and success of the query. The
problem with blocking execution that if there is a problem in the connection to
HS2 for a long running query (say wi-fi problems during the hours long wait),
then the operation handle is not obtained and there is no way to query for
state/sucess of the query.
With async execute option, as it does not block, the operation handle is
returned to the client immediately.
> ExecuteStatementAsync call to run a query in non-blocking mode
> --------------------------------------------------------------
>
> Key: HIVE-4617
> URL: https://issues.apache.org/jira/browse/HIVE-4617
> Project: Hive
> Issue Type: Improvement
> Components: HiveServer2
> Affects Versions: 0.12.0
> Reporter: Jaideep Dhok
> Assignee: Vaibhav Gumashta
> Attachments: HIVE-4617.D12417.1.patch, HIVE-4617.D12417.2.patch,
> HIVE-4617.D12417.3.patch, HIVE-4617.D12417.4.patch, HIVE-4617.D12417.5.patch,
> HIVE-4617.D12417.6.patch, HIVE-4617.D12507.1.patch,
> HIVE-4617.D12507Test.1.patch
>
>
> Provide a way to run a queries asynchronously. Current executeStatement call
> blocks until the query run is complete.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
