pvillard31 commented on a change in pull request #4405:
URL: https://github.com/apache/nifi/pull/4405#discussion_r457229134
##########
File path: nifi-docs/src/main/asciidoc/user-guide.adoc
##########
@@ -755,14 +755,19 @@ the parallelization that NiFi uses to process the data.
However, there are sever
is one in which each incoming FlowFile contains references to several other
data items, such as a list of files in a directory. The user may want to
process the entire listing before allowing any other data to enter the Process
Group.
+When the FlowFile Concurrency is configured to "Single Batch Per Node," the
Input Ports will behave similarly to the way that they behave in the
Review comment:
```suggestion
When the FlowFile Concurrency is configured to "Single Batch Per Node", the
Input Ports will behave similarly to the way that they behave in the
```
##########
File path: nifi-docs/src/main/asciidoc/user-guide.adoc
##########
@@ -755,14 +755,19 @@ the parallelization that NiFi uses to process the data.
However, there are sever
is one in which each incoming FlowFile contains references to several other
data items, such as a list of files in a directory. The user may want to
process the entire listing before allowing any other data to enter the Process
Group.
+When the FlowFile Concurrency is configured to "Single Batch Per Node," the
Input Ports will behave similarly to the way that they behave in the
+"Single FlowFile Per Node" mode, but when a FlowFile is ingested, the Input
Ports will continue to ingest all data until all of the queues feeding
+the Input Ports have been emptied. At that point, they will not bring any more
data into the Process Group until all data has finished processing and
+has left the Process Group (see note on <<Connecting_Batch_Oriented_Groups>>
below).
+
NOTE: The FlowFile Concurrency controls only when data will be pulled into the
Process Group from an Input Port. It does not prevent a Processor within the
Process Group from ingesting data from outside of NiFi.
While the FlowFile Concurrency dictates how data should be brought into the
Process Group, the Outbound Policy controls the flow of data out of the Process
Group.
There are two available options for the Outbound Policy: "Stream When
Available" and "Batch Output". The default value is "Stream When Available."
When this mode is used,
Review comment:
```suggestion
There are two available options for the Outbound Policy: "Stream When
Available" and "Batch Output". The default value is "Stream When Available".
When this mode is used,
```
##########
File path: nifi-docs/src/main/asciidoc/user-guide.adoc
##########
@@ -744,8 +744,8 @@ information or context about the Process Group.
[[Flowfile_Concurrency]]
=== FlowFile Concurrency
-FlowFile Concurrency is used to control how data is brought into the Process
Group. There are two options available: Unbounded (which is the default)
-and Single FlowFile Per Node. When the concurrency is set to "Unbounded," the
Input Ports in the Process Group will ingest data as quickly as they
+FlowFile Concurrency is used to control how data is brought into the Process
Group. There are three options available: Unbounded (which is the default),
+Single FlowFile Per Node, and Single Batch Per Node. When the concurrency is
set to "Unbounded," the Input Ports in the Process Group will ingest data as
quickly as they
are able, provided that backpressure does not prevent them from doing so.
When the FlowFile Concurrency is configured to "Single FlowFile Per Node," the
Input Ports will only allow through a single FlowFile at at time.
Review comment:
```suggestion
When the FlowFile Concurrency is configured to "Single FlowFile Per Node",
the Input Ports will only allow through a single FlowFile at at time.
```
##########
File path: nifi-docs/src/main/asciidoc/user-guide.adoc
##########
@@ -778,6 +783,25 @@ batch.output.B = 1, batch.output.C = 2, batch.output.D = 0.
The Outbound Policy of "Batch Output" doesn't provide any benefits when used
in conjunction with a FlowFile Concurrency of "Unbounded."
Review comment:
```suggestion
The Outbound Policy of "Batch Output" doesn't provide any benefits when used
in conjunction with a FlowFile Concurrency of "Unbounded".
```
##########
File path: nifi-docs/src/main/asciidoc/user-guide.adoc
##########
@@ -778,6 +783,25 @@ batch.output.B = 1, batch.output.C = 2, batch.output.D = 0.
The Outbound Policy of "Batch Output" doesn't provide any benefits when used
in conjunction with a FlowFile Concurrency of "Unbounded."
As a result, the Outbound Policy is ignored if the FlowFile Concurrency is set
to "Unbounded."
Review comment:
```suggestion
As a result, the Outbound Policy is ignored if the FlowFile Concurrency is
set to "Unbounded".
```
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
