You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by GitBox <gi...@apache.org> on 2022/11/02 12:46:51 UTC
[GitHub] [nifi-minifi-cpp] szaszm commented on a diff in pull request #1439: MINIFICPP-1967 Add batch processing of lines in TailFile
szaszm commented on code in PR #1439:
URL: https://github.com/apache/nifi-minifi-cpp/pull/1439#discussion_r1011706756
##########
PROCESSORS.md:
##########
@@ -2424,6 +2424,7 @@ In the list below, the names of required properties appear in bold. Any other pr
| State File | TailFileState | | Specifies the file that should be used for storing state about what data has been ingested so that upon restart NiFi can resume from where it left off |
| tail-base-directory | | | Base directory used to look for files to tail. This property is required when using Multiple file mode. Can contain expression language placeholders if Attribute Provider Service is set.<br/>**Supports Expression Language: true** |
| **tail-mode** | Single file | Single file<br>Multiple file<br> | Specifies the tail file mode. In 'Single file' mode only a single file will be watched. In 'Multiple file' mode a regex may be used. Note that in multiple file mode we will still continue to watch for rollover on the initial set of watched files. The Regex used to locate multiple files will be run during the schedule phrase. Note that if rotated files are matched by the regex, those files will be tailed. |
+| **Batch Size** | 0 | | Maximum number of lines to process in a single trigger. If set to 0 all new lines will be processed. |
Review Comment:
I would update the property name as well. This leaves the door open for a future property that controls how many lines are emitted in a single flow file, with a similar same name.
--
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.
To unsubscribe, e-mail: issues-unsubscribe@nifi.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org