[
https://issues.apache.org/jira/browse/JCR-2415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12985560#action_12985560
]
Sébastien Launay commented on JCR-2415:
---------------------------------------
> It would certainly be nice to get to the point where Lucene 3.0.x could be
> used.
Definitely, I'll see if I can find a way to keep the Adapter pattern and use
String[Ord]ValComparator.
> Some proposed changes/fixes
Indeed from what I have seen these changes look complementary so do not
hesitate to commit them, that's why I created a topic branch at first.
> Do you know how this change should affect query performance ? Should it
> improve, or will it degrade ?
I think performance will be better because the new Lucene classes are more
complex in order to be more efficient (this is typically the case for
FieldComparator [1] which render migration difficult).
One thing I'm sure is that the index size on disk will be larger because we no
longer compress stored field larger than 16K.
Jukka's performance test suite will be handy to produce performance numbers
before/after the migration.
[1]
http://lucene.apache.org/java/3_0_3/api/core/org/apache/lucene/search/FieldComparator.html
> Update Lucene to 3.0
> --------------------
>
> Key: JCR-2415
> URL: https://issues.apache.org/jira/browse/JCR-2415
> Project: Jackrabbit Content Repository
> Issue Type: Improvement
> Components: query
> Affects Versions: 2.0-beta3
> Reporter: Attila Király
> Attachments: cumulative.patch, DocIdSetIterator.patch, review.patch
>
>
> Lucene 3.0 was released on 2009/11/25. They migrated to Java 1.5 as
> Jackrabbit is doing with 2.0. Also they added some new optimizations. It
> would be nice if Jackrabbit could switch to the new lucene version too.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
