[
https://issues.apache.org/jira/browse/HIVE-8568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14185907#comment-14185907
]
Mohit Sabharwal commented on HIVE-8568:
---------------------------------------
Thanks, [~vgumashta]! I hadn't considered expanding GetOperationStatus. I agree
that we should try re-use existing methods before adding a new API.
I looked at GetOperationStatus and seems to me that it will make code more
complicated to add this method there. As you point out, this call is polling on
a running Operation's state, which is set (in Operation) before or after
executing the query (i.e. before or after driver.run()). However, setting the
jobIDs in OperationState during currently running MR/Tez tasks would mean
making the Operation reference available to the Driver/DriverContext.
Alternatively, we could add operation.getJobIDs in
CliServer.getOperationStatus(), however, that seems pretty unclean as those are
two separate operations.
Overall I think, keeping the two APIs separate is also cleaner (and less
surprising to users) since most users interested in polling for operation
status are not interested in JobIDs.
Let me know what you think. Thanks!
> Add HS2 API to fetch Job IDs for a given query
> ----------------------------------------------
>
> Key: HIVE-8568
> URL: https://issues.apache.org/jira/browse/HIVE-8568
> Project: Hive
> Issue Type: Bug
> Reporter: Mohit Sabharwal
> Assignee: Mohit Sabharwal
> Attachments: HIVE-8568.1.patch, HIVE-8568.patch
>
>
> Fetching Job IDs corresponding to all running MR/Tez tasks is useful for
> clients like Hue.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
