[ https://issues.apache.org/jira/browse/LUCENE-5405?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Benson Margulies updated LUCENE-5405: ------------------------------------- Fix Version/s: 4.7 > 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 > Fix For: 5.0, 4.7 > > Attachments: LUCENE-5405-4.x.patch > > > 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: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org