[
https://issues.apache.org/jira/browse/NIFI-744?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14705365#comment-14705365
]
Aldrin Piri commented on NIFI-744:
----------------------------------
Did a good bit of investigation on this and changes look good. +1
On an important note from the standpoint of verifying backward compatibility
echoing some of Joe's thoughts, I think we need test resources for whatever
versions of swap we have available and create and make tests that explicitly
show the compatibility between versions. I see there is a generic backward
compatibility test, but feel this probably needs to be duplicated to compare
versions. The code looks reasonable to handle all this but it's not something
that is readily apparent without some inspection.
> Allow FileSystemRepository to write to the same file for multiple
> (non-parallel) sessions
> -----------------------------------------------------------------------------------------
>
> Key: NIFI-744
> URL: https://issues.apache.org/jira/browse/NIFI-744
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
> Reporter: Mark Payne
> Assignee: Mark Payne
> Fix For: 0.3.0
>
> Attachments:
> 0001-NIFI-744-Refactored-ContentClaim-into-ContentClaim-a.patch
>
>
> Currently, when a ProcessSession is committed, the Content Claim that was
> being written to is now "finished" and will never be written to again.
> When a flow has processors that generate many, many FlowFiles, each in their
> own session, this means that we have many, many files on disk on the Content
> Repository, as well. Generally, this hasn't been a problem to write to these
> files. However, when the files are to be archived or destroyed, this is very
> taxing and can cause erratic performance.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
