[
https://issues.apache.org/jira/browse/HUDI-233?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17002591#comment-17002591
]
Vinoth Chandar commented on HUDI-233:
-------------------------------------
I dont have the actual stacktraces.. but mostly you could run into issues with
version conflicts or slf4j finding multiple bindings..
In general, the approach I took when redoing all the bundles, were to try and
use the logging classes in the underlying system (spark, presto, hive etc) as
much as possible, and only shade if its absolutely needed.. May be we can
follow the same approach?
> 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
> Affects Versions: 0.5.0
> Reporter: Vinoth Chandar
> Assignee: leesf
> Priority: Major
> Fix For: 0.5.2
>
>
> 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)
