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] [Updated] (LUCENE-5684) Add best effort detection when index is removed & recreated before openIfChanged
Date Mon, 19 May 2014 21:01:39 GMT

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

Michael McCandless updated LUCENE-5684:
---------------------------------------

    Attachment: LUCENE-5684.patch

Another iteration, more simplifications, I think it's ready.

> Add best effort detection when index is removed & recreated before openIfChanged
> --------------------------------------------------------------------------------
>
>                 Key: LUCENE-5684
>                 URL: https://issues.apache.org/jira/browse/LUCENE-5684
>             Project: Lucene - Core
>          Issue Type: Improvement
>            Reporter: Michael McCandless
>            Assignee: Michael McCandless
>             Fix For: 4.9, 5.0
>
>         Attachments: LUCENE-5684.patch, LUCENE-5684.patch
>
>
> I dug into the confusing NPE from the java-user email with subject "[lucene 4.6] NPE
when calling IndexReader#openIfChanged".
> It happens because the app was opening an IndexReader, then rm -rf the entire index,
build a new one, then calling reopen.  This is invalid usage (the app should instead use IW.deleteAll,
or open new IW with OpenMode.CREATE), but I'd like to add a minor best effort check...



--
This message was sent by Atlassian JIRA
(v6.2#6252)

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


Mime
View raw message