[
https://issues.apache.org/jira/browse/HIVE-5217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13817046#comment-13817046
]
Carl Steinbach commented on HIVE-5217:
--------------------------------------
bq. It wouldn't be too hard to add support for a non long polling
getOperationStatus call in future, specially a non rpc call.
Adding a getOperationStatusInternal() or getOperationStatusNonLongPoll() method
to work around this problem is exactly the sort of thing I want to avoid. This
patch implements a service layer feature, so I think it makes sense that the
implementation belongs in the service layer as well. In
CLIService.getOperationStatus() you have access to the SessionManager, and from
that you can easily get the Session object, the Operation object, the operation
type, and the Session's configuration. As an added bonus you also get the
OperationHandle which makes it easier to emit useful log messages that
reference the session and operation IDs.
> 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-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)
