You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@nifi.apache.org by "ASF subversion and git services (Jira)" <ji...@apache.org> on 2023/03/03 13:34:00 UTC

[jira] [Commented] (NIFI-11094) Allow CaptureChangeMySQL to send multiple events per FlowFile

    [ https://issues.apache.org/jira/browse/NIFI-11094?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17696155#comment-17696155 ] 

ASF subversion and git services commented on NIFI-11094:
--------------------------------------------------------

Commit be4d2d4e1cad32138ad5fdb597ffd3651f602e11 in nifi's branch refs/heads/support/nifi-1.x from Matt Burgess
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=be4d2d4e1c ]

NIFI-11094: Allow CaptureChangeMySQL to send multiple events per FlowFile

This closes #6907.

Co-authored-by: Tamas Palfy <tp...@apache.org>

Signed-off-by: Tamas Palfy <tp...@apache.org>


> Allow CaptureChangeMySQL to send multiple events per FlowFile
> -------------------------------------------------------------
>
>                 Key: NIFI-11094
>                 URL: https://issues.apache.org/jira/browse/NIFI-11094
>             Project: Apache NiFi
>          Issue Type: Improvement
>            Reporter: Matt Burgess
>            Assignee: Matt Burgess
>            Priority: Major
>             Fix For: 2.0.0
>
>          Time Spent: 2h 20m
>  Remaining Estimate: 0h
>
> It would be nice if there could be a Events Per FlowFile Strategy property for CaptureChangeMySQL that could allow for things like N events per FlowFile or one full transaction per FlowFile. It can help lower overhead downstream and increase the overall performance of the flow.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)