[ https://issues.apache.org/jira/browse/SOLR-5623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13868364#comment-13868364 ]
Robert Muir commented on SOLR-5623: ----------------------------------- I'm not completely opposed to it for the record, i'm just saying "i dont know about it". At the very least ill say, i'd be less opposed in trunk because the logic there it is simpler (due to java7 try-with: no boolean success/success2 heh). Still, as an API i dont like the fact that we'd be wrapping some specific exception with a bogus-generic one... > Better diagnosis of RuntimeExceptions in analysis > ------------------------------------------------- > > Key: SOLR-5623 > URL: https://issues.apache.org/jira/browse/SOLR-5623 > Project: Solr > Issue Type: Bug > Reporter: Benson Margulies > > If an analysis component (tokenizer, filter, etc) gets really into a hissy > fit and throws a RuntimeException, the resulting log traffic is less than > informative, lacking any pointer to the doc under discussion (in the doc > case). It would be more better if there was a catch/try shortstop that logged > this more informatively. -- This message was sent by Atlassian JIRA (v6.1.5#6160) --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org