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

ASF subversion and git services commented on NIFI-6182:
-------------------------------------------------------

Commit f15332ff87b2aee04a87c8577184294d662bd020 in nifi's branch 
refs/heads/master from Mark Payne
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=f15332f ]

NIFI-6182: Updated dependency on Lucene to Lucene 8.0.0. Updated code necessary 
to use the new API. Updated WriteAheadProvenanceRepository so that upon startup 
if provenance indexes are written using the old Lucene format, , they are 
considered 'defunct' and the events are re-indexed in a background thread into 
a new index that uses the Lucene 8 format and the old index is then removed. 
Added Provenance Repository that consists of about 30 events and added 
integration test to ensure that the repo can be started up/initialized when 
pointing to a prov repo that was written using the old lucene format.


> Update Provenance Repository to use Lucene 8.x
> ----------------------------------------------
>
>                 Key: NIFI-6182
>                 URL: https://issues.apache.org/jira/browse/NIFI-6182
>             Project: Apache NiFi
>          Issue Type: Improvement
>          Components: Core Framework
>            Reporter: Mark Payne
>            Assignee: Mark Payne
>            Priority: Major
>             Fix For: 1.10.0
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> The Provenance Repository is built against a rather old version of Apache 
> Lucene (4.x, I believe). The current version is 8.0. We should update to the 
> latest to ensure that we are able to take advantage of all newest features 
> and ensure that if any vulnerabilities are discovered, that they will be 
> dealt with. Having very old dependencies generally makes it very hard to 
> address any vulnerabilities or failures that occur.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to