You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@hudi.apache.org by "sivabalan narayanan (Jira)" <ji...@apache.org> on 2021/11/19 15:57:00 UTC

[jira] [Updated] (HUDI-1707) Improve Logging subsystem

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

sivabalan narayanan updated HUDI-1707:
--------------------------------------
    Fix Version/s: 0.11.0
                       (was: 0.10.0)

> Improve Logging subsystem
> -------------------------
>
>                 Key: HUDI-1707
>                 URL: https://issues.apache.org/jira/browse/HUDI-1707
>             Project: Apache Hudi
>          Issue Type: Improvement
>          Components: Code Cleanup
>            Reporter: Volodymyr Burenin
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 0.11.0
>
>
> Currently Hudi has a relatively verbose logging on info level that is not particularly useful. Like latency measurements of file system views, print out of commit timelines, etc that could be super large, etc.
> Additionally to that, the logging subsystem is suboptimal as it formats all messages before they are being passed into the logger, so it doesn't matter if logger will or will not print out a log message a lot of work is still being done anyway.
> Would be also nice to add more messages on info level to determine at which phase Hudi is: ideally, the info level should be limited to the point that just looking into the logs should be clear enough at which phase Hudi is and what it is doing without being too verbose.
> TBD: Add more thoughts on logging subsystem



--
This message was sent by Atlassian Jira
(v8.20.1#820001)