[HUDI-233] Redo log statements using SLF4J

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 0.5.0
• Component/s: code-quality
• Labels: new-to-hudi pull-request-available
• Assignee: leesf
• Reporter: Vinoth Chandar
• Created: 30/Aug/19 16:12
• Updated: 16/Jan/22 06:29
• Resolved: 03/Nov/21 05:40

Description

Currently we are not employing variable substitution aggresively in the project. ala

LogManager.getLogger(SomeName.class.getName()).info("Message: {}, Detail: {}", message, detail);

This can improve performance since the string concatenation is deferrable to when the logging is actually in effect.

Issue Links

• is a parent of: HUDI-454 Redo hudi-cli log statements using SLF4J
• is a parent of: HUDI-457 Redo hudi-common log statements using SLF4J
• is a parent of: HUDI-458 Redo hudi-hadoop-mr log statements using SLF4J
• is a parent of: HUDI-459 Redo hudi-hive log statements using SLF4J
• is a parent of: HUDI-460 Redo hudi-integ-test log statements using SLF4J
• is a parent of: HUDI-461 Redo hudi-spark log statements using SLF4J
• is a parent of: HUDI-462 Redo hudi-timeline-service log statements using SLF4J
• is a parent of: HUDI-463 Redo hudi-utilities log statements using SLF4J
• is a parent of: HUDI-455 Redo hudi-client log statements using SLF4J
• is a parent of: HUDI-456 Redo hudi-common log statements using SLF4J
• is depended upon by: HUDI-1237 [UMBRELLA] Checkstyle, formatting, warnings, spotless
• links to: GitHub Pull Request #1135