[
https://issues.apache.org/jira/browse/HIVE-5217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vaibhav Gumashta updated HIVE-5217:
-----------------------------------
Description: [HIVE-4617|https://issues.apache.org/jira/browse/HIVE-4617]
provides support for async execution in HS2. The client gets an operation
handle which it can poll to check on the operation status. However, the polling
frequency is entirely left to the client which can be resource inefficient.
Long polling will solve this, by blocking the client request to check the
operation status for a configurable amount of time (a new HS2 config) if the
data is not available, but responding immediately if the data is available.
(was: [HIVE-4617|https://issues.apache.org/jira/browse/HIVE-4617] provides
support for async execution in HS2. The client gets an operation handle which
it can poll to check on the operation status. However, the polling frequency is
entirely left to the client which can be resource inefficient. Long polling
will solve this by blocking the client request to check the operation status
for a configurable amount of time (a new HS2 config) if the data is not
available, but responding immediately if the data is available.)
> Add long polling to asynchronous execution in HiveServer2
> ---------------------------------------------------------
>
> Key: HIVE-5217
> URL: https://issues.apache.org/jira/browse/HIVE-5217
> Project: Hive
> Issue Type: Improvement
> Components: HiveServer2
> Affects Versions: 0.12.0
> Reporter: Vaibhav Gumashta
> Assignee: Vaibhav Gumashta
>
> [HIVE-4617|https://issues.apache.org/jira/browse/HIVE-4617] provides support
> for async execution in HS2. The client gets an operation handle which it can
> poll to check on the operation status. However, the polling frequency is
> entirely left to the client which can be resource inefficient. Long polling
> will solve this, by blocking the client request to check the operation status
> for a configurable amount of time (a new HS2 config) if the data is not
> available, but responding immediately if the data is available.
--
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
