[jira] [Updated] (HUDI-755) Modify lo4j properties to allow execution of tests in debug log mode

["Ramachandran M S (Jira)" <ji...@apache.org>]

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

Ramachandran M S updated HUDI-755:
----------------------------------
    Status: Open  (was: New)

> Modify lo4j properties to allow execution of tests in debug log mode
> --------------------------------------------------------------------
>
>                 Key: HUDI-755
>                 URL: https://issues.apache.org/jira/browse/HUDI-755
>             Project: Apache Hudi (incubating)
>          Issue Type: Sub-task
>            Reporter: Ramachandran M S
>            Assignee: Ramachandran M S
>            Priority: Minor
>
> Currently tests run at the log level of WARN. This skips some of the code paths that will be run if debug logging it turned on for production. Since some of the code inside the debug section is critical and could break production if not tested, we need to run tests at debug log level mode.
>  
> But we also need to maintain a balance to not log DEBUG & INFO logs to console so as to not overwhelm the log file size. Travis has a cap of 4MB per log file size. So we need to enable code execution at DEBUG level but only log WARN+ to console.



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