[
https://issues.apache.org/jira/browse/NIFI-4262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16113544#comment-16113544
]
ASF GitHub Bot commented on NIFI-4262:
--------------------------------------
GitHub user pvillard31 opened a pull request:
https://github.com/apache/nifi/pull/2056
NIFI-4262 - MergeContent - option to add merged uuid in original flow…
… files
Thank you for submitting a contribution to Apache NiFi.
In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:
### For all changes:
- [ ] Is there a JIRA ticket associated with this PR? Is it referenced
in the commit message?
- [ ] Does your PR title start with NIFI-XXXX where XXXX is the JIRA number
you are trying to resolve? Pay particular attention to the hyphen "-" character.
- [ ] Has your PR been rebased against the latest commit within the target
branch (typically master)?
- [ ] Is your initial contribution a single, squashed commit?
### For code changes:
- [ ] Have you ensured that the full suite of tests is executed via mvn
-Pcontrib-check clean install at the root nifi folder?
- [ ] Have you written or updated unit tests to verify your changes?
- [ ] If adding new dependencies to the code, are these dependencies
licensed in a way that is compatible for inclusion under [ASF
2.0](http://www.apache.org/legal/resolved.html#category-a)?
- [ ] If applicable, have you updated the LICENSE file, including the main
LICENSE file under nifi-assembly?
- [ ] If applicable, have you updated the NOTICE file, including the main
NOTICE file found under nifi-assembly?
- [ ] If adding new Properties, have you added .displayName in addition to
.name (programmatic access) for each of the new properties?
### For documentation related changes:
- [ ] Have you ensured that format looks appropriate for the output in
which it is rendered?
### Note:
Please ensure that once the PR is submitted, you check travis-ci for build
issues and submit an update to your PR as soon as possible.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/pvillard31/nifi NIFI-4262
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/nifi/pull/2056.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #2056
----
commit bf77df17e8e00d32e1f71922774cf68dd6ba8c2d
Author: Pierre Villard <[email protected]>
Date: 2017-08-03T21:40:48Z
NIFI-4262 - MergeContent - option to add merged uuid in original flow files
----
> 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)
