[
https://issues.apache.org/jira/browse/HIVE-4570?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13668023#comment-13668023
]
Carl Steinbach edited comment on HIVE-4570 at 5/28/13 3:29 AM:
---------------------------------------------------------------
bq. Current API GetOperationState is not enough since it returns only a state
enum. Instead of changing that we can add new API GetOperationProgress() which
will return both OperationState and OperationProgress.
The HS2 RPCs were designed to be extensible, which is why they take a single
Thrift struct as input and return a single Thrift struct as output. One of the
motivations for this is the Metastore Thrift API which suffers from a
proliferation of nearly identical RPCs, e.g. get_tables(), get_all_tables(),
get_table(), etc, etc. I don't see any advantage to adding a new RPC over the
alternative of extending the GetOperationState() input and output structs. The
same holds for ExecuteStatement() vs. ExecuteStatementAsync().
I have some other comments about the approach outlined above, but I'm going to
make them in HIVE-4569 in the interest of consolidating this discussion in one
place.
was (Author: cwsteinbach):
bq. Current API GetOperationState is not enough since it returns only a
state enum. Instead of changing that we can add new API GetOperationProgress()
which will return both OperationState and OperationProgress.
The HS2 RPCs were designed to be extensible, which is why they take a single
Thrift struct as input and return a single Thrift struct as output. One of the
motivations for this is the Metastore Thrift API which suffers from a
proliferation of nearly identical RPCs, e.g. get_tables(), get_all_tables(),
get_table(), etc, etc. I don't see any advantage to adding a new RPC over the
alternative of extending the GetOperationState() input and output structs. The
same holds for ExecuteStatement() vs. ExecuteStatementAsync().
> More information to user on GetOperationStatus in Hive Server2 when query is
> still executing
> --------------------------------------------------------------------------------------------
>
> Key: HIVE-4570
> URL: https://issues.apache.org/jira/browse/HIVE-4570
> Project: Hive
> Issue Type: Improvement
> Components: HiveServer2
> Affects Versions: 0.11.0
> Reporter: Amareshwari Sriramadasu
> Assignee: Jaideep Dhok
>
> Currently in Hive Server2, when the query is still executing only the status
> is set as STILL_EXECUTING.
> This issue is to give more information to the user such as progress and
> running job handles, if possible.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
