[
https://issues.apache.org/jira/browse/IMPALA-14735?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18057851#comment-18057851
]
Zoltán Borók-Nagy commented on IMPALA-14735:
--------------------------------------------
I see, I assume one part of the issue is that the impala-shell doesn't send the
SET command to the coordinator, but instead it maintains a map of query options
that it sends with each statement.
This code only runs if the coordinator receives a SET request:
[https://github.com/apache/impala/blob/3be15fd3598071eaeddd9b4d29e0883b95fdd14a/be/src/service/client-request-state.cc#L348-L352]
So apart from setting the configuration during OpenSession, the impala-shell
might still need to send a SET request for a subset of query options (including
idle_session_timeout).
> impala-shell should send configuration with HS2 OpenSession
> -----------------------------------------------------------
>
> Key: IMPALA-14735
> URL: https://issues.apache.org/jira/browse/IMPALA-14735
> Project: IMPALA
> Issue Type: Improvement
> Components: Clients
> Reporter: Michael Smith
> Priority: Major
>
> Currently impala-shell sends no configuration when setting up an HS2 session.
> This prevents setting session-wide query options, and in particular provides
> no way to set session-specific configuration such as
> {{idle_session_timeout}}. We should send all query options set as
> impala-shell CLI flags with OpenSession.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
