lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (LUCENE-5405) Exception strategy for analysis improved
Date Sun, 02 Feb 2014 20:48:09 GMT

    [ https://issues.apache.org/jira/browse/LUCENE-5405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13889050#comment-13889050
] 

ASF subversion and git services commented on LUCENE-5405:
---------------------------------------------------------

Commit 1563711 from [~bmargulies] in branch 'dev/trunk'
[ https://svn.apache.org/r1563711 ]

LUCENE-5405: check in the unit test, that escaped the first time.

closes #21.

> 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
>
>
> 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-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


Mime
View raw message