[
https://issues.apache.org/jira/browse/NIFI-4972?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16398275#comment-16398275
]
ASF GitHub Bot commented on NIFI-4972:
--------------------------------------
GitHub user ijokarumawak opened a pull request:
https://github.com/apache/nifi/pull/2543
NIFI-4972: SelectHiveQL to emit FETCH provenance event
SelectHiveQL should emit FETCH instead of CONTENT_MODIFIED when it has
incoming connections.
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:
- [x] Is there a JIRA ticket associated with this PR? Is it referenced
in the commit message?
- [x] 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.
- [x] Has your PR been rebased against the latest commit within the target
branch (typically master)?
- [x] 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?
- [x] 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/ijokarumawak/nifi nifi-4972
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/nifi/pull/2543.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 #2543
----
commit a66820d53fa747e567099a702cd26e254cf51cb8
Author: Koji Kawamura <ijokarumawak@...>
Date: 2018-03-14T08:42:10Z
NIFI-4972: SelectHiveQL to emit FETCH provenance event
SelectHiveQL should emit FETCH instead of CONTENT_MODIFIED when it has
incoming connections.
----
> SelectHiveQL should emit FETCH provenance event instead of CONTENT_MODIFIED
> when it has input connections
> ---------------------------------------------------------------------------------------------------------
>
> Key: NIFI-4972
> URL: https://issues.apache.org/jira/browse/NIFI-4972
> Project: Apache NiFi
> Issue Type: Bug
> Components: Extensions
> Affects Versions: 1.5.0
> Reporter: Koji Kawamura
> Assignee: Koji Kawamura
> Priority: Major
>
> SelectHiveQL generates RECEIVE provenance events when it does not have input
> connections.
> But it generates CONTENT_MODIFIED with input connections.
> CONTENT_MODIFIED event does not have transitUri. This impacts NiFi and Atlas
> integration scenario as ReportLineageToAtlas will not able to report lineage.
> This issue was originally found by [~nayakmahesh616].
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
