You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by pvillard31 <gi...@git.apache.org> on 2017/11/02 09:17:48 UTC
[GitHub] nifi pull request #2234: NIFI-4548: Add REMOTE_INVOCATION provenance event t...
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?
---