[
https://issues.apache.org/jira/browse/LUCENE-6217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14305961#comment-14305961
]
ASF subversion and git services commented on LUCENE-6217:
---------------------------------------------------------
Commit 1657399 from [~mikemccand] in branch 'dev/branches/branch_5x'
[ https://svn.apache.org/r1657399 ]
LUCENE-6217: add IW.isOpen and IW.getTragicException
> 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: [email protected]
For additional commands, e-mail: [email protected]
