[
https://issues.apache.org/jira/browse/NIFI-3522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15879337#comment-15879337
]
ASF GitHub Bot commented on NIFI-3522:
--------------------------------------
GitHub user markap14 opened a pull request:
https://github.com/apache/nifi/pull/1532
NIFI-3522: When creating a clone of a FlowFile, ensure that we proper…
…ly set the 'updated attributes' on the RepositoryRecord to all attributes
on the FlowFile itself, the same way we do when calling create(FlowFile)
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/markap14/nifi NIFI-3522
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/nifi/pull/1532.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 #1532
----
commit e3e99ca5e6e41993dc70a6c44db71307d9a7d8fe
Author: Mark Payne <[email protected]>
Date: 2017-02-22T22:02:56Z
NIFI-3522: When creating a clone of a FlowFile, ensure that we properly set
the 'updated attributes' on the RepositoryRecord to all attributes on the
FlowFile itself, the same way we do when calling create(FlowFile)
----
> If a Processor clones a FlowFile then adds attributes to or modifies the
> clone, a Provenance Event is generated with no FlowFile UUID.
> --------------------------------------------------------------------------------------------------------------------------------------
>
> Key: NIFI-3522
> URL: https://issues.apache.org/jira/browse/NIFI-3522
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
> Reporter: Mark Payne
> Assignee: Mark Payne
>
> This can be recreated by adding a SplitText Processor to the canvas and then
> feeding it in a FlowFile that does not need to be split. In this case, a
> Provenance CLONE event is generated, and so is an ATTRIBUTES_MODIFIED event
> because after cloning the incoming FlowFile, we add attributes to the clone.
> If we then attempt to query provenance for events generated by this Processor
> - or use the Provenance Reporting Task - we will get an error indicating that
> the Provenance Event could not be generated because it has no FlowFile UUID.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
