[
https://issues.apache.org/jira/browse/NIFI-1279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15064183#comment-15064183
]
Mark Payne commented on NIFI-1279:
----------------------------------
The supplied patch here gets us 'closer' to the correct answer, but it could
still be improved. If two FlowFiles have the same lineage start date, we will
now look at the one-up ID of the FlowFile to make a determination about its
old-ness / new-ness. However, we should be able to examine also the one-up id
of the lineage starting flowfile. A ticket has been created for this: NIFI-1306.
> OldestFlowFileFirst, NewestFlowFileFirst prioritizers don't work if two
> FlowFiles have same timestamp
> -----------------------------------------------------------------------------------------------------
>
> Key: NIFI-1279
> URL: https://issues.apache.org/jira/browse/NIFI-1279
> Project: Apache NiFi
> Issue Type: Bug
> Components: Extensions
> Reporter: Mark Payne
> Assignee: Mark Payne
> Fix For: 0.4.1
>
> Attachments:
> 0001-NIFI-1279-Take-the-FlowFile-s-1-up-id-into-account-f.patch
>
>
> The OldestFlowFileFirst and NewestFlowFileFirst prioritizers perform their
> prioritization based on the lineage start date of FlowFiles. It is quite
> possible to have multiple FlowFiles with the same lineage start date, but
> they should still be ordered properly based on their FlowFile Identifier
> (which is a 1-up integer for each FlowFile).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
