[
https://issues.apache.org/jira/browse/NIFI-4638?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16285928#comment-16285928
]
Joseph Witt commented on NIFI-4638:
-----------------------------------
These are good findings and it will be good to get to the bottom of it.
Probably comes down to one or a combination of the timing at which events are
generated (same millisecond, etc..) which could cause insertion ordering
ambiguity and use of other data structures which are not doing any
prioritization/ordering.
> Drop events disordering
> -----------------------
>
> Key: NIFI-4638
> URL: https://issues.apache.org/jira/browse/NIFI-4638
> Project: Apache NiFi
> Issue Type: Bug
> Reporter: Omer Hadari
>
> Drop events that are generated by terminated relationships alongside other
> event types are sometimes registered before them. This happens since the drop
> event’s timestamp is lower by a millisecond compared to the timestamp of the
> other event, even though the ordinal is higher. This causes the lineage graph
> to look as if the other event comes out of the drop event.
> The one millisecond difference and the fact that this bug is sporadic
> suggests a rollover to the next millisecond when registering the event before
> the drop event.
> For example this was encountered in the split json processor, when the
> original flowfile receives a fragment count and then dropped. This could be a
> bug in the processor itself, though it seems to be more generic.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
