[ https://issues.apache.org/jira/browse/NIFI-4774?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16397267#comment-16397267 ]
ASF subversion and git services commented on NIFI-4774: ------------------------------------------------------- Commit d14229e4407ce4587ba422fbd85e15a9d4f66f85 in nifi's branch refs/heads/master from [~markap14] [ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=d14229e ] NIFI-4774: Allow user to choose which write-ahead log implementation should be used by the WriteAheadFlowFileRepository Removed TODO comment Signed-off-by: Matthew Burgess <mattyb...@apache.org> This closes #2487 > FlowFile Repository should write updates to the same FlowFile to the same > partition > ----------------------------------------------------------------------------------- > > Key: NIFI-4774 > URL: https://issues.apache.org/jira/browse/NIFI-4774 > Project: Apache NiFi > Issue Type: Bug > Components: Core Framework > Reporter: Mark Payne > Assignee: Mark Payne > Priority: Major > Fix For: 1.6.0 > > > As-is, in the case of power loss or Operating System crash, we could have an > update that is lost, and then an update for the same FlowFile that is not > lost, because the updates for a given FlowFile can span partitions. If an > update were written to Partition 1 and then to Partition 2 and Partition 2 is > flushed to disk by the Operating System and then the Operating System crashes > or power is lost before Partition 1 is flushed to disk, we could lose the > update to Partition 1. -- This message was sent by Atlassian JIRA (v7.6.3#76005)