You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues-all@impala.apache.org by "Manish Maheshwari (Jira)" <ji...@apache.org> on 2023/01/19 13:57:00 UTC

[jira] [Updated] (IMPALA-3951) Define different error codes for expired session vs invalid session for ODBC/JDBC clients

     [ https://issues.apache.org/jira/browse/IMPALA-3951?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Manish Maheshwari updated IMPALA-3951:
--------------------------------------
    Labels: 2023Q1  (was: )

> 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: issues-all-unsubscribe@impala.apache.org
For additional commands, e-mail: issues-all-help@impala.apache.org