[
https://issues.apache.org/jira/browse/NIFI-2087?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15378114#comment-15378114
]
ASF subversion and git services commented on NIFI-2087:
-------------------------------------------------------
Commit 2540573d77c026585eed03bf0d7cd2f042bb1df2 in nifi's branch
refs/heads/master from [~markap14]
[ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=2540573 ]
NIFI-2087: Do not update the lucene index to delete expired events. Instead,
just wait for the entire index to expire and remove the files for that index.
This is much more efficient.
This closes #652
Signed-off-by: jpercivall <[email protected]>
> Provenance Repository still removing events from Lucene Index
> -------------------------------------------------------------
>
> Key: NIFI-2087
> URL: https://issues.apache.org/jira/browse/NIFI-2087
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
> Reporter: Mark Payne
> Assignee: Mark Payne
> Fix For: 1.0.0
>
>
> NIFI-756 was implemented in NiFi 0.3.0 to change the way in which we remove
> events from the Lucene Indexes. It appears, though, that we still are using
> the DeleteIndexAction to remove events from the Lucene Index, in addition to
> the code that was added. As a result, we are removing events from the lucene
> index, in addition to the newer mechanism of just deleting the index files
> when they are no longer relevant.
> We should be able to simply stop using the DeleteIndexAction in
> PersistentProvenanceRepository and then test by starting NiFi with a small
> index shard size (say 25 MB), create a lot of data, such that some of the
> data ages off. We should then be able to verify that queries no longer show
> the data and be able to look in the provenance repository directory to verify
> that the old index-* directories are getting deleted.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
