[
https://issues.apache.org/jira/browse/LUCENE-5405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13886091#comment-13886091
]
ASF subversion and git services commented on LUCENE-5405:
---------------------------------------------------------
Commit 1562657 from [~bmargulies] in branch 'dev/trunk'
[ https://svn.apache.org/r1562657 ]
LUCENE-5405: when there's an exception thrown by an analysis component, note
the field name
on the info stream to aid in debugging.
> Exception strategy for analysis improved
> ----------------------------------------
>
> Key: LUCENE-5405
> URL: https://issues.apache.org/jira/browse/LUCENE-5405
> Project: Lucene - Core
> Issue Type: Improvement
> Reporter: Benson Margulies
> Assignee: Benson Margulies
>
> SOLR-5623 included some conversation about the dilemmas of exception
> management and reporting in the analysis chain.
> I've belatedly become educated about the infostream, and this situation is a
> job for it. The DocInverterPerField can note exceptions in the analysis
> chain, log out to the infostream, and then rethrow them as before. No
> wrapping, no muss, no fuss.
> There are comments on this JIRA from a more complex prior idea that readers
> might want to ignore.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
