[ 
https://issues.apache.org/jira/browse/NIFI-7773?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17771349#comment-17771349
 ] 

Eric Secules commented on NIFI-7773:
------------------------------------

Nifi queues without any extra configuration do not make any guarantees about 
processing order. You should consider adding an enforce order processor  
[https://nifi.apache.org/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.5.0/org.apache.nifi.processors.standard.EnforceOrder|https://nifi.apache.org/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.5.0/org.apache.nifi.processors.standard.EnforceOrder]
 / between the jolt processor and the put database processor and use an 
appropriate priority attribute prioritizer between enforce order and the 
database update.

> JoltTransformJSON mixing up flow files order
> --------------------------------------------
>
>                 Key: NIFI-7773
>                 URL: https://issues.apache.org/jira/browse/NIFI-7773
>             Project: Apache NiFi
>          Issue Type: Bug
>          Components: Core Framework
>    Affects Versions: 1.11.4
>         Environment: Ubuntu 16 x64, 3 nodes cluster
>            Reporter: Dmytro Kulyk
>            Priority: Critical
>              Labels: jolt, order
>         Attachments: Sportsbook (2).json, image-2020-08-28-13-06-03-269.png, 
> image-2020-08-28-13-06-20-964.png, image-2020-08-28-13-07-39-001.png
>
>
> Using *JoltTransformJSON* to transform (flatten/rename fields) kafka JSON 
> messages before making an update on Postgres DB
> In some rare cases messages (received from same topic partition) are "mixing" 
> up an order within a *same node*
>  Therefore updates are invoked in wrong order, affecting on data consistency 
> and correctness
> *Provenance* logs for some found cases:
> Partition and offset for each message provided in screen (with blue)
>  !image-2020-08-28-13-06-03-269.png|width=726,height=478!
>  !image-2020-08-28-13-06-20-964.png|width=730,height=417! 
> *Flow* (mentioned "flow pipeline" marked with yellow):
>  !image-2020-08-28-13-07-39-001.png|width=728,height=389!
> *Flow code* has been attached



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to