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 "Thomas Tauber-Marshall (Jira)" <ji...@apache.org> on 2021/03/23 21:43:00 UTC

[jira] [Created] (IMPALA-10604) Allow setting KuduClient's verbose logging level directly

Thomas Tauber-Marshall created IMPALA-10604:
-----------------------------------------------

             Summary: Allow setting KuduClient's verbose logging level directly
                 Key: IMPALA-10604
                 URL: https://issues.apache.org/jira/browse/IMPALA-10604
             Project: IMPALA
          Issue Type: Improvement
    Affects Versions: Impala 4.0
            Reporter: Thomas Tauber-Marshall
            Assignee: Thomas Tauber-Marshall


Currently, Impala sets KuduClient's verbose logging level to the same as its own level (taken from the -v flag) minus 1. Since KuduClient doesn't have any way of setting vmodule, this means that to get verbose logging inside KuduClient users must turn it on to a high level for all of Impala, which can produce an enormous volume of logging. making it hard to collect, share, and analyze logs.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscribe@impala.apache.org
For additional commands, e-mail: issues-all-help@impala.apache.org