The concept of being able to provide hints to the underlying content
repository about which content is more important to keep longer than
others is a good one. I'd recommend filing a JIRA for the ask and
providing your proposed concept as one to consider.
Definitely see something like this being useful but I suspect we'll
want to consider alternative approaches like having such hints about
retention be placed on the processors that create/modify/touch the
data because when you consider that most flows are graphs and
non-linear the decisions about retention become more complex.
Thanks
On Wed, May 17, 2017 at 12:40 PM, Juan Sequeiros <helloj...@gmail.com> wrote:
> All,
>
> On latest NIFI can we archive only specific FlowFiles based on an attribute?
> I can put in a feature request if not.
>
> For instance:
>
> archive.max.retention.period=12 hours
> archive.max.retention.attributes.period=5 days
> archive.retention.attributes=${some.special.attribute.for.my.longer.retention}
>
> Then everything is archived for 12 hours unless the flowFile is set with an
> attribute that would be configured through
> archive.max.retention.attributes.period
>
> And have archive.max.usage.percentage=50% ( supersede everything else )
>
> Thank you
