hive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mohit Sabharwal (JIRA)" <>
Subject [jira] [Commented] (HIVE-8568) Add HS2 API to fetch Job IDs for a given query
Date Mon, 27 Oct 2014 22:07:34 GMT


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
 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:
>             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

This message was sent by Atlassian JIRA

View raw message