[
https://issues.apache.org/jira/browse/NIFI-14752?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18005513#comment-18005513
]
ASF subversion and git services commented on NIFI-14752:
--------------------------------------------------------
Commit ffaa98c2ea652d694c5926f444851dcfc399020c in nifi's branch
refs/heads/main from David Handermann
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=ffaa98c2ea ]
NIFI-14752 Added Max Uncommitted Size to ConsumeKafka
- Updated Offset Tracker to calculate Total Record Size based on Kafka Consumer
Record key and value length
Signed-off-by: Pierre Villard <[email protected]>
This closes #10093.
> Add Max Uncommitted Size Property to ConsumeKafka
> -------------------------------------------------
>
> Key: NIFI-14752
> URL: https://issues.apache.org/jira/browse/NIFI-14752
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Extensions
> Reporter: David Handermann
> Assignee: David Handermann
> Priority: Major
> Time Spent: 20m
> Remaining Estimate: 0h
>
> The {{ConsumeKafka}} Processor should be updated with a new property named
> {{Max Uncommitted Size}} to provide an optional boundary for the total size
> of records consumed from Kafka in a single invocation.
> The current {{Max Uncommitted Time}} property defines the total amount of
> time that {{ConsumeKafka}} should spend before transferring FlowFiles to an
> output relationship, but some of that time spent may be unnecessary if the
> desired size of records consumed provides an earlier threshold.
> The new {{Max Uncommitted Size}} property should not be required, maintaining
> compatibility with existing Processor configuration. The property should
> support standard data size validation.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
