Michael McCandless created LUCENE-6279:
------------------------------------------
Summary: 3.x -> 4.x .si upgrade should not be tricked by leftover
upgrade marker file
Key: LUCENE-6279
URL: https://issues.apache.org/jira/browse/LUCENE-6279
Project: Lucene - Core
Issue Type: Bug
Reporter: Michael McCandless
Assignee: Michael McCandless
Fix For: 4.10.x
Today when you do the first IW.commit to a 3.x index from Lucene 4.x, we go
through a per-segment upgrade process when writing the next segments_N
file, writing .si files for each segment if we didn't already do so.
However, this process can be fooled by a leftover _N_upgraded.si
file, in case the app above Lucene wasn't careful and reused a
directory that had leftover files... I think we can make this more
robust.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
