[
https://issues.apache.org/jira/browse/IMPALA-13745?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Quanlong Huang updated IMPALA-13745:
------------------------------------
Description:
We have different client RPCs to close a query or get the profile of it. If we
want to get the final profile, we'd better close the query first in case
coordinator is still handling profile updates from executors. However, after
closing the query, the profile might be discarded shortly in a busy cluster
that has lots of queries. Client might miss the chance to fetch the profile.
In HS2 protocol, Impala provides CloseImpalaOperation RPC which is currently
used to close a DML operation and return the DML summary.
{code:java}
// Same as HS2 CloseOperation but can return additional information.
TCloseImpalaOperationResp CloseImpalaOperation(1:TCloseImpalaOperationReq
req);{code}
As [~csringhofer] mentioned in the code review of
[https://gerrit.cloudera.org/c/22457/2//COMMIT_MSG#27], we can consider
extending it to close a query and return the final profile.
was:
We have different client RPCs to close a query or get the profile of it. If we
want to get the final profile, we'd better close the query first in case
coordinator is still handling profile updates from executors. However, after
closing the query, the profile might be discarded shortly in a busy cluster
that has lots of queries. Client might miss the chance to fetch the profile.
In HS2 protocol, Impala provides CloseImpalaOperation RPC which is currently
used to close a DML operation and return the DML summary.
{code}
// Same as HS2 CloseOperation but can return additional information.
TCloseImpalaOperationResp CloseImpalaOperation(1:TCloseImpalaOperationReq
req);{code}
We can consider extending it to close a query and return the final profile.
> Extends CloseImpalaOperation to support returning the final profile
> -------------------------------------------------------------------
>
> Key: IMPALA-13745
> URL: https://issues.apache.org/jira/browse/IMPALA-13745
> Project: IMPALA
> Issue Type: New Feature
> Components: Backend, Clients
> Reporter: Quanlong Huang
> Priority: Major
>
> We have different client RPCs to close a query or get the profile of it. If
> we want to get the final profile, we'd better close the query first in case
> coordinator is still handling profile updates from executors. However, after
> closing the query, the profile might be discarded shortly in a busy cluster
> that has lots of queries. Client might miss the chance to fetch the profile.
> In HS2 protocol, Impala provides CloseImpalaOperation RPC which is currently
> used to close a DML operation and return the DML summary.
> {code:java}
> // Same as HS2 CloseOperation but can return additional information.
> TCloseImpalaOperationResp CloseImpalaOperation(1:TCloseImpalaOperationReq
> req);{code}
> As [~csringhofer] mentioned in the code review of
> [https://gerrit.cloudera.org/c/22457/2//COMMIT_MSG#27], we can consider
> extending it to close a query and return the final profile.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
