[
https://issues.apache.org/jira/browse/HIVE-25107?focusedWorklogId=597948&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-597948
]
ASF GitHub Bot logged work on HIVE-25107:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 17/May/21 18:15
Start Date: 17/May/21 18:15
Worklog Time Spent: 10m
Work Description: abstractdog commented on pull request #2271:
URL: https://github.com/apache/hive/pull/2271#issuecomment-842226170
merged, thanks for the review @pgaref
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
Issue Time Tracking
-------------------
Worklog Id: (was: 597948)
Time Spent: 40m (was: 0.5h)
> Classpath logging should be on DEBUG level
> ------------------------------------------
>
> Key: HIVE-25107
> URL: https://issues.apache.org/jira/browse/HIVE-25107
> Project: Hive
> Issue Type: Improvement
> Reporter: László Bodor
> Assignee: László Bodor
> Priority: Major
> Labels: pull-request-available
> Fix For: 4.0.0
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> 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
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
