[
https://issues.apache.org/jira/browse/HIVE-5217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14047301#comment-14047301
]
Lefty Leverenz commented on HIVE-5217:
--------------------------------------
*hive.server2.long.polling.timeout* is documented in the wiki here:
* [Configuration Properties: hive.server2.long.polling.timeout |
https://cwiki.apache.org/confluence/display/Hive/Configuration+Properties#ConfigurationProperties-hive.server2.long.polling.timeout]
> Add long polling to asynchronous execution in HiveServer2
> ---------------------------------------------------------
>
> Key: HIVE-5217
> URL: https://issues.apache.org/jira/browse/HIVE-5217
> 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-5217.2.patch, HIVE-5217.3.patch, HIVE-5217.4.patch,
> HIVE-5217.5.patch, HIVE-5217.6.patch, HIVE-5217.D12801.2.patch,
> HIVE-5217.D12801.3.patch, HIVE-5217.D12801.4.patch, HIVE-5217.D12801.5.patch,
> HIVE-5217.D12801.6.patch
>
>
> [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 was sent by Atlassian JIRA
(v6.2#6252)
