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

ASF subversion and git services commented on NIFI-4972:
-------------------------------------------------------

Commit d3f54994a6510b5a428f30e65b3d456225749937 in nifi's branch 
refs/heads/master from [~ijokarumawak]
[ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=d3f5499 ]

NIFI-4972 - SelectHiveQL to emit FETCH provenance event

SelectHiveQL should emit FETCH instead of CONTENT_MODIFIED when it has
incoming connections.

Signed-off-by: Pierre Villard <[email protected]>

This closes #2543.


> 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)

Reply via email to