[jira] [Comment Edited] (SOLR-5623) Better diagnosis of RuntimeExceptions in analysis
[ https://issues.apache.org/jira/browse/SOLR-5623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13868400#comment-13868400 ] Benson Margulies edited comment on SOLR-5623 at 1/11/14 7:59 PM: - [~hossman_luc...@fucit.org] I think the patch request is now good to go, again sticking with a Solr change and considering a Lucene change later on. was (Author: bmargulies): I think the patch request is now good to go, again sticking with a Solr change and considering a Lucene change later on. > 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
[jira] [Comment Edited] (SOLR-5623) Better diagnosis of RuntimeExceptions in analysis
[ https://issues.apache.org/jira/browse/SOLR-5623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13868347#comment-13868347 ] Benson Margulies edited comment on SOLR-5623 at 1/10/14 9:46 PM: - [~rcmuir] The identity of the field we are processing is known down in Lucene core. What do you think about wrapping Throwables in org.apache.lucene.index.DocInverterPerField.processFields in some specific runtime exception that carries the field name? Then I can in turn make it into a Solr exception in DirectUpdateHandler2. was (Author: bmargulies): [~rcmuir] The identity of the field we are processing is known down in Lucene core. What do you think about wrapping generic Throwables in org.apache.lucene.index.DocInverterPerField.processFields in some specific runtime exception that carries the field name? Then I can in turn make it into a Solr exception in DirectUpdateHandler2. > 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
