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

["Thomas Tauber-Marshall (Jira)" <ji...@apache.org>]

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

Thomas Tauber-Marshall resolved IMPALA-10604.
---------------------------------------------
    Fix Version/s: Impala 4.0
       Resolution: Fixed

> 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
>            Priority: Major
>             Fix For: Impala 4.0
>
>
> 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)