You are viewing a plain text version of this content. The canonical link for it is here.
Posted to oak-issues@jackrabbit.apache.org by "Tommaso Teofili (JIRA)" <ji...@apache.org> on 2017/07/06 08:20:00 UTC
[jira] [Commented] (OAK-6412) Consider upgrading to newer Lucene
versions
[ https://issues.apache.org/jira/browse/OAK-6412?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16076148#comment-16076148 ]
Tommaso Teofili commented on OAK-6412:
--------------------------------------
In the context of potential switch to Lucene 7, here's an interesting blogpost: http://blog.mikemccandless.com/2017/07/lucene-gets-concurrent-deletes-and.html?spref=tw
> Consider upgrading to newer Lucene versions
> -------------------------------------------
>
> Key: OAK-6412
> URL: https://issues.apache.org/jira/browse/OAK-6412
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: lucene
> Reporter: Tommaso Teofili
> Assignee: Tommaso Teofili
> Fix For: 1.8
>
>
> An year ago I had started prototyping the upgrade to Lucene 5 [1], in the meantime version 6 (and 7 soon) has come out.
> I think it'd be very nice to upgrade Lucene version to the latest, this would give us improvements in space consumption and runtime performance.
> In case we want to upgrade to 6.0 or later we need to consider upgrade scenarios because Lucene Codecs are backward compatible with the previous major release, so Lucene 6 can read Lucene 5 but not Lucene 4.x (4.7 in our case) therefore we would need to detect that when reading an index and trigger reindexing using the new format.
> Related to that there's also a patch to upgrade Solr index to version 5 (see OAK-4318).
> [1] : https://github.com/tteofili/jackrabbit-oak/tree/lucene5
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)