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

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

Github user mattyb149 commented on a diff in the pull request:

    https://github.com/apache/nifi/pull/2056#discussion_r133019004
  
    --- Diff: 
nifi-nar-bundles/nifi-extension-utils/nifi-processor-utils/src/main/java/org/apache/nifi/processor/util/bin/BinFiles.java
 ---
    @@ -94,6 +96,16 @@
                 .addValidator(StandardValidators.createTimePeriodValidator(1, 
TimeUnit.SECONDS, Integer.MAX_VALUE, TimeUnit.SECONDS))
                 .build();
     
    +    public static final PropertyDescriptor ADD_MERGED_UUID = new 
PropertyDescriptor.Builder()
    --- End diff --
    
    I talked this over with @markap14 as well, it seems like just adding an 
attribute here is a better user experience than adding another property to 
offer a choice. I presume it was to offer the current behavior as well, which 
normally is a good thing so as not to upset existing flows, but I think in this 
case you could just add it (and document it). New attributes on split flowfiles 
might affect memory, but for merged flow files it should not be an issue. What 
do you think?


> 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
>
> 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
(v6.4.14#64029)

Reply via email to