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

Benjamin Habegger commented on OAK-12089:
-----------------------------------------

So we decided to move to an alternate option. Migrating from 4 to 5, then 5 to 
6, etc. Seems very cubersome.

The alternative path is to introduce a new luceneNg implementation along side 
the existing legacy one. The goal of this implementation would be to be less 
depedendant on a specific lucene version (even though the initial 
implementation would use lucene 9). 

This new could then be released in "beta" along side the existing one as a 
separate sling bundle. This way it can be tested in multiple derisked 
environments. Once  validated that the new implementation is stable a more 
generalized migration could be envisaged and then the legacy lucene could be 
deprecated, and then removed. Eventually and if needed the legacy lucene code 
could be maintained elsewhere and embedded where it might still be necessary.

> Upgrade Lucene to a more recent version
> ---------------------------------------
>
>                 Key: OAK-12089
>                 URL: https://issues.apache.org/jira/browse/OAK-12089
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>            Reporter: Benjamin Habegger
>            Priority: Major
>
> Currently OAK is using version 4.7.2 which dates back to Apr 14, 2014 (+10 
> years old), that is no longer supported and has required Lucene to be 
> embedded vulnerabilities are fixed.
> Current supported versions are 9.x and 10.x. The goal of this ticket is to 
> progress on upgrading Lucene to a more recent version. 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to