[
https://issues.apache.org/jira/browse/LUCENE-2675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12915492#action_12915492
]
Robert Muir commented on LUCENE-2675:
-------------------------------------
in my opinion this would be very confusing and set a bad precedent.
I don't understand how it would make migration easier... migration backwards?
Personally I think we should let things be... e.g. someone will get confused
and think they
can open their 3.0-created index with 2.9/java 1.4 but it is a different
version of Unicode, for example.
> Add support for 3.0 indexes in 2.9 branch
> -----------------------------------------
>
> Key: LUCENE-2675
> URL: https://issues.apache.org/jira/browse/LUCENE-2675
> Project: Lucene - Java
> Issue Type: Improvement
> Affects Versions: 2.9, 2.9.1, 2.9.2, 2.9.3
> Reporter: Uwe Schindler
> Assignee: Uwe Schindler
> Priority: Minor
> Fix For: 2.9.4
>
> Attachments: index.30.cfs.zip, index.30.nocfs.zip, LUCENE-2675.patch
>
>
> There was a lot of user requests to be able to read Lucene 3.0 indexes also
> with 2.9. This would make the migration easier. There is no problem in doing
> that, as the new stored fields version in Lucene 3.0 is only used to mark a
> segment's stored fields file as no longer containing compressed fields. But
> index format did not really change. This patch simply allows FieldsReader to
> pass a Lucene 3.0 version number, but still writes segments in 2.9 format (as
> you could suddenly turn on compression for added documents).
> I added ZIP files for 3.0 indexes for TestBackwards. Without the patch it
> does not pass, as FieldsReader complains about incorrect version number
> (although it could read the file easily). If we would release maybe a 2.9.4
> release of Lucene we should include that patch.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
