[
https://issues.apache.org/jira/browse/NIFI-744?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14701322#comment-14701322
]
Mark Payne commented on NIFI-744:
---------------------------------
[~brianghig]: I am in the process of creating a new patch that is built against
the 'master' branch, as that is what the community has decided to switch to.
Once I have that patch created, I will upload it here.
I added quite a few unit tests to test all of the corner cases that I could
come up with, as well as the regular functionality. I've had it running on a
test cluster for several weeks now without issue. It's really just a matter of
stressing it out, hitting it from every angle that we can. Since it hasn't been
officially released yet, I won't recommend pushing it to your production
environment, but if you want to use the patch to push to a dev/test environment
to ensure that all behaves as expected, then that would be great.
> 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
>
>
> 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)
