[jira] [Assigned] (IMPALA-11435) impala-shell gets "No handlers could be found for logger" from Thrift code

["Peter Rozsa (Jira)" <ji...@apache.org>]

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

Peter Rozsa reassigned IMPALA-11435:
------------------------------------

    Assignee: Peter Rozsa

> impala-shell gets "No handlers could be found for logger" from Thrift code
> --------------------------------------------------------------------------
>
>                 Key: IMPALA-11435
>                 URL: https://issues.apache.org/jira/browse/IMPALA-11435
>             Project: IMPALA
>          Issue Type: Bug
>          Components: Clients
>    Affects Versions: Impala 4.2.0
>            Reporter: Joe McDonnell
>            Assignee: Peter Rozsa
>            Priority: Major
>
> In some configurations (e.g. SSL), impala-shell will complain about logging not being configured at connect time:
> {noformat}
> No handlers could be found for logger "thrift.transport.sslcompat"{noformat}
> Impala-shell doesn't use Python's logging package, so it currently doesn't initialize logging. However, Thrift's python library does use the logging package, which leads to this message when running the code from impala-shell.
> One option would be for impala-shell to initialize Python logging in its main function:
> {noformat}
> logging.basicConfig(level=logging.CRITICAL){noformat}
> We would have to be careful to make sure that Thrift messages don't interfere with expected output (or duplicate current output). Another option would be to disable logging entirely:
> {noformat}
> logging.disable(logging.CRITICAL){noformat}



--
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