[
https://issues.apache.org/jira/browse/IMPALA-3951?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17681994#comment-17681994
]
Manish Maheshwari commented on IMPALA-3951:
-------------------------------------------
Workaround - Tableau has its own idle timeout config
(vizqlserver.protocolcachelifetime_in_minutes) with a default value of 120
mins. By making the Tableau idle timeout set to 15 mins and increasing the
Impala idle timeout to 30 mins, we saw ALL Tableau sessions closed in the
Impala web UI as well as frontend service threads getting closed as well.
Solution going forward is to have Tableau's timeout always be less than
Impala's session timeout.
> Define different error codes for expired session vs invalid session for
> ODBC/JDBC clients
> -----------------------------------------------------------------------------------------
>
> Key: IMPALA-3951
> URL: https://issues.apache.org/jira/browse/IMPALA-3951
> Project: IMPALA
> Issue Type: Improvement
> Components: Clients
> Affects Versions: Impala 2.2.4
> Reporter: Mala Chikka Kempanna
> Priority: Minor
> Labels: 2023Q1
>
> We right now have only one error code that we return to JDBC ODBC clients for
> both expired session and invalid session.
> const char* ImpalaServer::SQLSTATE_GENERAL_ERROR = "HY000";
> Please define and return different error codes for different kind of session
> errors.
> Clients like Tableau read only error codes and do not parse the actual error
> messages. It will help them code appropriately on their end and make decision
> of whether to retry or re-establish new session if different error codes are
> returned to clients connected on 21050 port.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
