[ 
https://issues.apache.org/jira/browse/LUCENE-5377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13878604#comment-13878604
 ] 

Shai Erera commented on LUCENE-5377:
------------------------------------

Isn't it then a problem of anyone that will try to addIndexes a pre-4.6 index 
to a 4.6+?

I looked at TestBackCompat.addOldIndexes - it doesn't do anything with the 
added index to verify it's OK. I added 
{{DirectoryReader.open(targetDir).close();}} to the test after {{w.close()}}, 
so at least we verify the index can be opened, but the test doesn't fail, not 
sure why. The newest "oldNames" is 4.2 - shouldn't a 4.5 have been created when 
we released 4.6, since we changed the index format? But then a 4.0/4.2 index 
should equally fail to be added to a 4.6, right? So maybe this doesn't explain 
the failure to reproduce this error...

> Lucene 4.6 cause mixed version segments info file(.si) wrong
> ------------------------------------------------------------
>
>                 Key: LUCENE-5377
>                 URL: https://issues.apache.org/jira/browse/LUCENE-5377
>             Project: Lucene - Core
>          Issue Type: Bug
>          Components: core/index, modules/facet
>    Affects Versions: 4.6
>         Environment: windows/linux
>            Reporter: Littlestar
>         Attachments: TestCore_45.java, TestCore_46.java
>
>
> my old facet index create by Lucene version=4.2
> use indexChecker ok.
> now I upgrade to Lucene 4.6 and put some new records to index.
> then reopen index, some files in indexdir missing....
> no .si files.
> I debug into it,  new version format of segments.gen(segments_N) record bad 
> segments info.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to