[
https://issues.apache.org/jira/browse/SOLR-5021?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13702485#comment-13702485
]
Hoss Man commented on SOLR-5021:
--------------------------------
bq. So i discarded them (also for lucene tests!), because otherwise, infostream
is useless when working with unit tests.
bq. ... i dont think anyone (humans or machines) want to see TP messages
Hrmmm... i'm not following you here ... why would infostream be "useless when
working with unit tests" if these messages were logged? It seems like it could
be handy, when trying to track down problems in Solr tests, to be able to see
the testPoint asserts in the logs -- interleaved with other debug log messages
from Solr.
I realize this would be very verbose, hence i'm not suggesting we do it at INFO
or even DEBUG, but i'm not understanding why it would be bad to allow them to
be logged at TRACE?
> LoggingInfoStream should log TP messages using TRACE level
> ----------------------------------------------------------
>
> Key: SOLR-5021
> URL: https://issues.apache.org/jira/browse/SOLR-5021
> Project: Solr
> Issue Type: Improvement
> Reporter: Hoss Man
>
> SOLR-4977 added an awesome new LoggingInfoStream class, and wisely it does
> not output "TP" category messages because it logs everything at the INFO
> level -- but we could improve this to log TP messages at the TRACE level (and
> check if TRACE is enabled when ased if isEnabled("TP").
> That way people who do/don't want to see all the TP messages could control
> that based on whether the LoggingInfoStream logger level was set to
> allow/filter TRACE level log messages.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
