[
https://issues.apache.org/jira/browse/HUDI-233?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16936670#comment-16936670
]
leesf commented on HUDI-233:
----------------------------
Could I start the progress? For simplicity, I woluld like create an umbrella
ticket and split the redo work to sub-task according to the module, such as
Redo hudi-cli log statements using SLF4J.
Redo hudi-client log statements using SLF4J.
Redo hudi-common log statements using SLF4J.
...
Or just complete the whole redo work in this ticket.
and what do you think? cc [~vinoth]
> Redo log statements using SLF4J
> --------------------------------
>
> Key: HUDI-233
> URL: https://issues.apache.org/jira/browse/HUDI-233
> Project: Apache Hudi (incubating)
> Issue Type: Bug
> Components: newbie, Performance
> Affects Versions: 0.5.0
> Reporter: Vinoth Chandar
> Assignee: leesf
> Priority: Major
>
> Currently we are not employing variable substitution aggresively in the
> project. ala
> {code:java}
> LogManager.getLogger(SomeName.class.getName()).info("Message: {}, Detail:
> {}", message, detail);
> {code}
> This can improve performance since the string concatenation is deferrable to
> when the logging is actually in effect.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
