[jira] [Commented] (NIFI-7339) WriteAheadProvenanceRepository ignores "nifi.provenance.repository.rollover.time" property

["ASF subversion and git services (Jira)" <ji...@apache.org>]

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

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

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

NIFI-7339: Fixed bug that caused Write Ahead Provenance Repository not to rollover event files after specified time. Code cleanup. Updated some default properties.


> WriteAheadProvenanceRepository ignores "nifi.provenance.repository.rollover.time" property
> ------------------------------------------------------------------------------------------
>
>                 Key: NIFI-7339
>                 URL: https://issues.apache.org/jira/browse/NIFI-7339
>             Project: Apache NiFi
>          Issue Type: Bug
>          Components: Core Framework
>            Reporter: Mark Payne
>            Assignee: Mark Payne
>            Priority: Major
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> The Persistent Provenance Repository allows users to have the Event File roll over periodically based on the value of the "nifi.provenance.repository.rollover.time" property. However, this property is ignored in the WriteAheadProvenanceRepository.
> As a result, the repository may write to the same event file for months. This can be problematic for two reasons:
> 1) the Event Time Offset could eventually overflow after Integer.MAX_VALUE milliseconds have elapsed.
> 2) Events that are expected to be aged off after, say 24 hours, may be kept around much longer if not much data is written to the Provenance repository.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)