lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael McCandless (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (LUCENE-6217) IndexWriter should make it clear when tragedy strikes
Date Wed, 04 Feb 2015 21:08:36 GMT

     [ https://issues.apache.org/jira/browse/LUCENE-6217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Michael McCandless resolved LUCENE-6217.
----------------------------------------
       Resolution: Fixed
    Fix Version/s: 5.1
                   Trunk

> IndexWriter should make it clear when tragedy strikes
> -----------------------------------------------------
>
>                 Key: LUCENE-6217
>                 URL: https://issues.apache.org/jira/browse/LUCENE-6217
>             Project: Lucene - Core
>          Issue Type: Bug
>            Reporter: Michael McCandless
>            Assignee: Michael McCandless
>             Fix For: Trunk, 5.1
>
>         Attachments: LUCENE-6217.patch
>
>
> If you hit an exception at a "bad time" e.g. when writing files for a newly flushed segment,
IndexWriter declares it a tragedy and secretly closes itself as a side effect of the exception.
> Subsequent operations will throw an ACE with the exception that caused the tragedy as
its cause.
> This requires messy code, if you want to know when this happened to you, since the first
exception doesn't make it clear that it was "tragic".
> I think we should make it easier to know when this happens?
> Maybe we could instead throw a new exception (IWClosedByTragedy or something), or maybe
we add a getter (.getTragicException) to IW?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


Mime
View raw message