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

ASF GitHub Bot commented on NIFI-4262:
--------------------------------------

Github user markap14 commented on the issue:

    https://github.com/apache/nifi/pull/2056
  
    @pvillard31 the code looks good to me, though I'm not in a state to easily 
switch over my branch and merge. I'll try to get to it fairly soon but if 
anyone else has the review cycles, then please feel free to review/merge. 
Thanks!


> MergeContent - option to add merged uuid in original flow files
> ---------------------------------------------------------------
>
>                 Key: NIFI-4262
>                 URL: https://issues.apache.org/jira/browse/NIFI-4262
>             Project: Apache NiFi
>          Issue Type: Improvement
>          Components: Extensions
>            Reporter: Pierre Villard
>            Assignee: Pierre Villard
>            Priority: Major
>
> With the apparition of Wait/Notify processors it is now possible tackle new 
> challenges when it comes to synchronize the execution of different parts of 
> the workflow.
> The objective here is the following:
> Flow files are sent to a MergeContent processor. Merged flow files are then 
> sent to a processor A while original flow files are sent to a processor B. I 
> want to trigger processor B when and only when processor A has completed.
> To use the Wait/Notify approach, a common attribute must be available to be 
> used as a signal in the distributed cache. This JIRA is about adding a 
> processor property allowing a user to add the UUID of the merged flow file as 
> a new attribute of all the original flow files that are constituting the 
> merged flow file.
> The template attached to NIFI-4028 can be used for this use case. Note that 
> the fix for NIFI-4028 is needed to solve the use case described in this JIRA.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to