nifi-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mark Payne (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (NIFI-744) Allow FileSystemRepository to write to the same file for multiple (non-parallel) sessions
Date Fri, 21 Aug 2015 14:57:45 GMT

     [ https://issues.apache.org/jira/browse/NIFI-744?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Mark Payne updated NIFI-744:
----------------------------
    Attachment: 0001-NIFI-744-Addressed-feedback-from-review-mostly-addin.patch

> 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-Addressed-feedback-from-review-mostly-addin.patch,
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)

Mime
View raw message