lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Muir (JIRA)" <j...@apache.org>
Subject [jira] Commented: (LUCENE-2675) Add support for 3.0 indexes in 2.9 branch
Date Mon, 27 Sep 2010 22:03:33 GMT

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

Robert Muir commented on LUCENE-2675:
-------------------------------------

bq. Forget about Java versions

well its important to me, so I won't just forget about it. Especially to users that don't
know how their analysis works, 
they do not know that java 1.4 is unicode 3.x and java 5 is unicode 4.x and harmony java5
is unicode 5.2 and java 6 is unicode 6.0. 

But this is even just part of the issue, i don't think we should do this. it adds too much
confusion to be officially supported in any release.
furthermore its not like it can be duplicated with 4.0, i would be against adding 4.x index
support to 3.x also, forget about in a bugfix release.
historically lucene has been held back by backwards compatibility, lets not throw forward
compatibility into the mix.

bq. If we would not have removed compression in 3.0, the file format would have been identical.

a great example of why major release shouldn't be just removal of deprecations.



> 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: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


Mime
View raw message