[
https://issues.apache.org/jira/browse/NIFI-15904?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18078388#comment-18078388
]
ASF subversion and git services commented on NIFI-15904:
--------------------------------------------------------
Commit 7b2580042c616ecbe4d52e2924aba70f1cb45e84 in nifi's branch
refs/heads/main from David Handermann
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=7b2580042c6 ]
NIFI-15904 Fixed Lineage Start Index in Session.create() (#11205)
- Set explicit Lineage Start Index using FlowFile ID
- Set explicit Entry Date and Lineage Start Date on new FlowFiles
> StandardProcessSession.create() produces FlowFiles with ambigous Start
> Lineage Index
> ------------------------------------------------------------------------------------
>
> Key: NIFI-15904
> URL: https://issues.apache.org/jira/browse/NIFI-15904
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
> Affects Versions: 2.0.0, 2.9.0
> Reporter: David Handermann
> Assignee: David Handermann
> Priority: Major
> Time Spent: 20m
> Remaining Estimate: 0h
>
> The {{StandardProcessSession.create()}} method creates a new {{FlowFile}}
> without a parent, setting the entry date and lineage start date to the
> current time in milliseconds. The {{create()}} method does not set the
> Lineage Start Index, keeping the default value of 0. As a result of this
> behavior, it is possible for multiple {{FlowFile}} objects to be created with
> the same millisecond timestamp, making the lineage order unclear. The
> {{lineageStartIndex}} should be specified to an incrementing number to
> provide unambiguous ordering as documented in
> {{FlowFile.getLineageStartIndex()}}.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
