[ https://issues.apache.org/jira/browse/HIVE-25107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17343244#comment-17343244 ]
László Bodor commented on HIVE-25107: ------------------------------------- yeah, you're right, I think we have 2 options: having this on DEBUG level, or making this logging optional now I would prefer optional logging DEBUG pro: no need to introduce a new hive option DEBUG con: turns on all of the debug messages what we're not interested in optional pro: fine-grain control about logging these messages only optional con: +1 hive option (not a big deal I think) > Thread classpath logging should be optional > ------------------------------------------- > > 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 > > 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. > https://github.com/apache/hive/commit/a234475faa2cab2606f2a74eb9ca071f006998e2#diff-44b2ff3a3c4a6cfcaed0fcb40b74031844f8586e40a6f8261637e5ebcd558b73R4577 -- This message was sent by Atlassian Jira (v8.3.4#803005)