[
https://issues.apache.org/jira/browse/HIVE-5217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13822017#comment-13822017
]
Vaibhav Gumashta commented on HIVE-5217:
----------------------------------------
[~cwsteinbach] Uploaded a patch based on the feedback.
Regarding moving the long polling timeout logic, I have some comments where
I'll appreciate your feedback:
1. Moving that logic to CLIService would mean accessing some of the operation
logic within CLIService, and from the general design of CLIService it looks
like we wanted to avoid that.
2. This will also mean that the async nature moves to Operation (runAsync,
backgroundHandle) from SQLOperation.
What are your thoughts? Thanks for the feedback and discussion so far!
> 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.2.patch, HIVE-5217.3.patch, HIVE-5217.4.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.1#6144)
