[HIVE-25107] Classpath logging should be on DEBUG level

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 4.0.0-alpha-1
• Labels: pull-request-available
• Assignee: László Bodor
• Reporter: László Bodor
• Created: 12/May/21 12:36
• Updated: 17/Nov/22 08:47
• Resolved: 17/May/21 10:56

Description

This is since HIVE-21584

I have a 72M llap executor log file, then I grepped for only "thread class path", piped into a separate file and a result was a 22M file...1/3-1/4 of the file was classpath info which is not usable for most of the time. This overwhelming amount of classpath info is not needed, assuming that classpath issues are reproducible with more or less effort, user should be responsible for turning on this expensive logging on demand. Not to mention performance implications which cannot be ignored beyond a certain amount of log messages.

https://github.com/apache/hive/commit/a234475faa2cab2606f2a74eb9ca071f006998e2#diff-44b2ff3a3c4a6cfcaed0fcb40b74031844f8586e40a6f8261637e5ebcd558b73R4577

Issue Links

• is caused by: HIVE-21584 Java 11 preparation: system class loader is not URLClassLoader
• links to: GitHub Pull Request #2271