[
https://issues.apache.org/jira/browse/SOLR-2191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13026714#comment-13026714
]
David Smiley commented on SOLR-2191:
------------------------------------
Yes, lets do this! I was just about to log a bug when I found it's already
been reported. I had some stupid error in my solr config and it never got
logged. Because of the error, the core never got registered into the container.
And then when I went to do any queries, Solr kept telling me I didn't specify a
core name when I never had to before (using the default). I was in the twilight
zone for a while.
Mark, you're a committer yet you supplied a patch. Why didn't you simply
commit it? I heard on the dev list recently that Solr is supposedly CTR
(commit then review), yet we clearly act here as RTC. So even if RTC is it,
wouldn't there be some threshold to let simple things like this through without
a review?
> Change SolrException cstrs that take Throwable to default to
> alreadyLogged=false
> --------------------------------------------------------------------------------
>
> Key: SOLR-2191
> URL: https://issues.apache.org/jira/browse/SOLR-2191
> Project: Solr
> Issue Type: Bug
> Reporter: Mark Miller
> Fix For: Next
>
> Attachments: SOLR-2191.patch
>
>
> Because of misuse, many exceptions are now not logged at all - can be painful
> when doing dev. I think we should flip this setting and work at removing any
> double logging - losing logging is worse (and it almost looks like we lose
> more logging than we would get in double logging) - and bad
> solrexception/logging patterns are proliferating.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
