[
https://issues.apache.org/jira/browse/NIFI-372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brandon DeVries updated NIFI-372:
---------------------------------
Description:
Currently, FlowFile expiration is based on the time of entry to the system.
Often, it seems as though time of entry to the specific queue would be the more
desirable behavior. We'd like to see if we can add a strategy for FlowFile
expiration to support (at least) these two options, and others as seems
appropriate.
With 1.0.0 on the horizon, this might be a good time to evaluate this in case
it requires any fundamental changes.
Possibly Strategies:
* time in queue
* time in flow
* time in process group?
* others...?
was:
Currently, FlowFile expiration is based on the time of entry to the system.
Often, it seems as though time of entry to the specific queue would be the more
desirable behavior. We'd like to see if we can add a strategy for FlowFile
expiration to support (at least) these two options, and others as seems
appropriate,
Possibly Strategies:
* time in queue
* time in flow
* time in process group?
* others...?
> provide flowfile expiration strategy
> ------------------------------------
>
> Key: NIFI-372
> URL: https://issues.apache.org/jira/browse/NIFI-372
> Project: Apache NiFi
> Issue Type: New Feature
> Components: Core Framework
> Affects Versions: 0.6.1
> Reporter: Ben Icore
>
> Currently, FlowFile expiration is based on the time of entry to the system.
> Often, it seems as though time of entry to the specific queue would be the
> more desirable behavior. We'd like to see if we can add a strategy for
> FlowFile expiration to support (at least) these two options, and others as
> seems appropriate.
> With 1.0.0 on the horizon, this might be a good time to evaluate this in case
> it requires any fundamental changes.
> Possibly Strategies:
> * time in queue
> * time in flow
> * time in process group?
> * others...?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
