[
https://issues.apache.org/jira/browse/NIFI-13914?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17891657#comment-17891657
]
ASF subversion and git services commented on NIFI-13914:
--------------------------------------------------------
Commit 39ca75d868ffe0e7df465798a77c33e74d154b7c in nifi's branch
refs/heads/main from Mark Payne
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=39ca75d868 ]
NIFI-13914 Fixed FlowFile Prioritization for Stateless Execution (#9432)
Ensure that when data is enqueued in the StatelessFlowFileQueue we order the
data properly before adding to its internal queue. Added system tests to verify
that the data is properly ordered while running within stateless and properly
ordered when coming out, if using a FIFO prioritizer.
Signed-off-by: David Handermann <[email protected]>
> Stateless not honoring ProcessSession.transfer ordering
> -------------------------------------------------------
>
> Key: NIFI-13914
> URL: https://issues.apache.org/jira/browse/NIFI-13914
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
> Affects Versions: 2.0.0-M1, 2.0.0-M2, 2.0.0-M3, 2.0.0-M4
> Reporter: Mark Payne
> Assignee: Mark Payne
> Priority: Major
> Fix For: 2.0.0-M5
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Occasionally a Processor operates on a batch of FlowFiles instead of a single
> FlowFile. If it transfers the FlowFiles in a particular order, the Process
> Session is not honoring that ordering in stateless, which can result in the
> next processor receiving the data in the wrong order. For example, a source
> Processor might receive two FlowFiles in a single session and transfer the
> first, then the second, using `ProcessSession.transfer(FlowFile,
> Relationship)`. In this case, the ProcessSession properly updates the last
> queue date/index. But when the FlowFiles are transferred to the next
> StatelessFlowFileQueue, they are not provided in any particular order, and
> the stateless flowfile queue simply adds them in whatever order the given
> Collection iterates over them. This results in data being improperly
> re-ordered within a Stateless execution.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
