lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Yonik Seeley (JIRA)" <>
Subject [jira] [Commented] (LUCENE-4190) IndexWriter deletes non-Lucene files
Date Wed, 04 Jul 2012 19:52:34 GMT


Yonik Seeley commented on LUCENE-4190:

bq. Thats why i took this issue (and already committed, see the commits list)

Hmmm, I don't see any commits under this issue.  But searching the mailing list, I do see
that you correctly used the issue name in the commit log - so I guess we can chalk it up to
the recent ASF infra flakiness.

bq. tomorrow, ill revert my commit and go back to deleting all files

-1 to reverting, we've made progress!
> IndexWriter deletes non-Lucene files
> ------------------------------------
>                 Key: LUCENE-4190
>                 URL:
>             Project: Lucene - Java
>          Issue Type: Bug
>            Reporter: Michael McCandless
>            Assignee: Robert Muir
>             Fix For: 4.0, 5.0
>         Attachments: LUCENE-4190.patch, LUCENE-4190.patch
> Carl Austin raised a good issue in a comment on my Lucene 4.0.0 alpha blog post:
> IndexWriter will now (as of 4.0) delete all foreign files from the index directory. 
We made this change because Codecs are free to write to any files now, so the space of filenames
is hard to "bound".
> But if the user accidentally uses the wrong directory (eg c:/) then we will in fact delete
important stuff.
> I think we can at least use some simple criteria (must start with _, maybe must fit certain
pattern eg _<base36>(_X).Y), so we are much less likely to delete a non-Lucene file....

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message