[
https://issues.apache.org/jira/browse/NIFI-4548?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16235441#comment-16235441
]
ASF GitHub Bot commented on NIFI-4548:
--------------------------------------
Github user pvillard31 commented on a diff in the pull request:
https://github.com/apache/nifi/pull/2234#discussion_r148475531
--- Diff:
nifi-api/src/main/java/org/apache/nifi/provenance/ProvenanceReporter.java ---
@@ -317,6 +317,18 @@
void send(FlowFile flowFile, String transitUri, String details, long
transmissionMillis, boolean force);
/**
+ * Emits a Provenance Event of type {@link
ProvenanceEventType#REMOTE_INVOCATION}
+ * that indicates a remote invocation is requested to an external
endpoint using
+ * the given FlowFile. The external endpoint may exist in a remote or
a local system,
+ * but is external to NiFi.
+ * @param flowFile the FlowFile that was used to make the remote
invocation
+ * @param transitUri A URI that provides information about the System
and
+ * Protocol information over which the invocation occurred. The intent
of this
+ * field is to identify they type and target resource or object of the
invocation.
+ */
+ void invokeRemoteProcess(FlowFile flowFile, String transitUri);
--- End diff --
Should we also add a method with ``String details``? It's not necessary for
HDFS processors but I think it'll make sense for other processors that will
generate such events. What do you think?
> 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)
