[
https://issues.apache.org/jira/browse/NIFI-4548?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16236347#comment-16236347
]
ASF subversion and git services commented on NIFI-4548:
-------------------------------------------------------
Commit 2a69b35f12586da16288e1a6d5e1dd3562490b92 in nifi's branch
refs/heads/master from [~ijokarumawak]
[ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=2a69b35 ]
NIFI-4548: Add REMOTE_INVOCATION provenance event type
This commit includes changes to DeleteHDFS to report REMOTE_INVOCATION
event. In order to do so, the processor had to be changed to create
output FlowFile because a provenance event needs a FlowFile it
associates with.
Signed-off-by: Pierre Villard <[email protected]>
This closes #2234.
> Add REMOTE_INVOCATION provenance event type
> -------------------------------------------
>
> Key: NIFI-4548
> URL: https://issues.apache.org/jira/browse/NIFI-4548
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Core Framework
> Reporter: Koji Kawamura
> Assignee: Koji Kawamura
> Priority: Major
>
> There are different Provenance Event Type already, CREATE, SEND or RECEIVE
> ... etc. However, none of them can well describe activities such as deleting
> objects from external storage, or calling 3rd party APIs to do something.
> This JIRA proposes that NiFi to have additional 'REMOTE_INVOCATION'
> provenance event type to represent operations described above. By looking at
> 'REMOTE_INVOCATION' event type, processor type and its transit URL,
> users/other programs can understand what operation has been made.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
