[
https://issues.apache.org/jira/browse/NIFI-2378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15391127#comment-15391127
]
Joseph Witt commented on NIFI-2378:
-----------------------------------
[~nadih] Expired flow files are still available in the content repository
unless the archive is disabled. That combined with the provenance events for
them means you can recover them, analyze what gets expired, etc..
The point of expiration on a connection is purely to convey "Data in this
connection if it reached X age is no longer useful". You certainly don't have
to turn that on and could instead do backpressure and use route on attribute
with alt routing. You could instead of having the blunt instrument of
expiration setup rules to reroute data, etc..
> Flowfile Expiration Strategy
> ----------------------------
>
> Key: NIFI-2378
> URL: https://issues.apache.org/jira/browse/NIFI-2378
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Core Framework
> Reporter: n h
>
> Currently all expired flowfiles are deleted. No chance for more actions. Is
> it possible to somehow collect them for further process? For example through
> a selected custom Controller Service.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
