[
https://issues.apache.org/jira/browse/NIFI-2920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15609718#comment-15609718
]
Joseph Witt commented on NIFI-2920:
-----------------------------------
[~markap14] On the latest 0.7.1 release I can easily recreate what looks like
undesirable behavior. Just a simple GenerateFlowFile connecting to an
UpdateAttribute with archive turned off. As long as there is no swapping
things don't hang around in teh content repo. If the flow is configured such
that swapping is happening then things pile up in the content repo until a
restart occurs.
> Swapped FlowFiles are not removed from content repo when a queue is emptied.
> ----------------------------------------------------------------------------
>
> Key: NIFI-2920
> URL: https://issues.apache.org/jira/browse/NIFI-2920
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
> Affects Versions: 0.6.1
> Environment: Linux
> Reporter: Matthew Clarke
> Priority: Critical
>
> If a queue contains enough FlowFiles to trigger swapping to occur and a user
> selects "empty queue" or sets file expiration, only the content claims
> associated to FlowFiles that were not swapped get removed from the content
> repository. All other content claims are left in the content repository and
> are not moved to archive and/or purged.
> A restart of NiFi will produce app log messages about these unknown files
> left in the content repo and will at that time move them to archive or purge
> them.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
