You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@nifi.apache.org by ma...@apache.org on 2020/05/12 20:01:27 UTC
[nifi] branch master updated: NIFI-7413: Documented
REMOTE_INVOCATION provenance event type in user/dev guides
This is an automated email from the ASF dual-hosted git repository.
mattyb149 pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/nifi.git
The following commit(s) were added to refs/heads/master by this push:
new 6b73ea4 NIFI-7413: Documented REMOTE_INVOCATION provenance event type in user/dev guides
6b73ea4 is described below
commit 6b73ea48bc4d2b80e69ba37efa3a4c6ed8f80e6a
Author: Peter Gyori <pe...@gmail.com>
AuthorDate: Tue May 12 10:22:43 2020 +0200
NIFI-7413: Documented REMOTE_INVOCATION provenance event type in user/dev guides
Signed-off-by: Matthew Burgess <ma...@apache.org>
This closes #4267
---
nifi-docs/src/main/asciidoc/developer-guide.adoc | 1 +
nifi-docs/src/main/asciidoc/user-guide.adoc | 1 +
2 files changed, 2 insertions(+)
diff --git a/nifi-docs/src/main/asciidoc/developer-guide.adoc b/nifi-docs/src/main/asciidoc/developer-guide.adoc
index aca8b69..2c84b77 100644
--- a/nifi-docs/src/main/asciidoc/developer-guide.adoc
+++ b/nifi-docs/src/main/asciidoc/developer-guide.adoc
@@ -900,6 +900,7 @@ The different event types for provenance reporting are:
|FORK |Indicates that one or more FlowFiles were derived from a parent FlowFile
|JOIN |Indicates that a single FlowFile is derived from joining together multiple parent FlowFiles
|RECEIVE |Indicates a provenance event for receiving data from an external process. This Event Type is expected to be the first event for a FlowFile. As such, a Processor that receives data from an external source and uses that data to replace the content of an existing FlowFile should use the FETCH event type, rather than the RECEIVE event type
+|REMOTE_INVOCATION |Indicates that a remote invocation was requested to an external endpoint (e.g. deleting a remote resource). The external endpoint may exist in a remote or a local system, but is external to NiFi
|REPLAY |Indicates a provenance event for replaying a FlowFile. The UUID of the event indicates the UUID of the original FlowFile that is being replayed. The event contains one Parent UUID that is also the UUID of the FlowFile that is being replayed and one Child UUID that is the UUID of the a newly created FlowFile that will be re-queued for processing
|ROUTE |Indicates that a FlowFile was routed to a specified relationship and provides information about why the FlowFile was routed to this relationship
|SEND |Indicates a provenance event for sending data to an external process
diff --git a/nifi-docs/src/main/asciidoc/user-guide.adoc b/nifi-docs/src/main/asciidoc/user-guide.adoc
index 10a1c22..c965f1e 100644
--- a/nifi-docs/src/main/asciidoc/user-guide.adoc
+++ b/nifi-docs/src/main/asciidoc/user-guide.adoc
@@ -2594,6 +2594,7 @@ The provenance event types are:
|FORK |Indicates that one or more FlowFiles were derived from a parent FlowFile
|JOIN |Indicates that a single FlowFile is derived from joining together multiple parent FlowFiles
|RECEIVE |Indicates a provenance event for receiving data from an external process
+|REMOTE_INVOCATION |Indicates that a remote invocation was requested to an external endpoint (e.g. deleting a remote resource)
|REPLAY |Indicates a provenance event for replaying a FlowFile
|ROUTE |Indicates that a FlowFile was routed to a specified relationship and provides information about why the FlowFile was routed to this relationship
|SEND |Indicates a provenance event for sending data to an external process