[
https://issues.apache.org/jira/browse/HIVE-5217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13815012#comment-13815012
]
Carl Steinbach commented on HIVE-5217:
--------------------------------------
[~vaibhavgumashta] Version 5 of the patch won't apply cleanly on trunk. Can you
please rebase the patch and post a review request on RB?
One concern I have with the patch is that the delay period affects everyone who
calls SQLOperation.getStatus(). Ideally we would be able to limit this behavior
to remote clients only. I'm worried that at some point in the future we're
going to want to have a housekeeping or monitoring thread that periodically
calls getStatus() on all active operations, and we don't want getStatus() to
block in these types of situations. Would it be practical to relocate this
logic to the CLIService layer so that it only impacts CLIService clients?
> 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.13.0
> Reporter: Vaibhav Gumashta
> Assignee: Vaibhav Gumashta
> Fix For: 0.13.0
>
> Attachments: HIVE-5217.D12801.2.patch, HIVE-5217.D12801.3.patch,
> HIVE-5217.D12801.4.patch, HIVE-5217.D12801.5.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.1#6144)
