[jira] [Commented] (NIFI-4491) Make CaptureChangeMySQL a record-aware processor

["Matt Burgess (Jira)" <ji...@apache.org>]

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

Matt Burgess commented on NIFI-4491:
------------------------------------

Agreed, with the caveat that an outgoing record-based FlowFile should contain a single transaction if possible and prudent, regardless of the number of records within, in order to preserve behavior between source and target DBs.

> Make CaptureChangeMySQL a record-aware processor
> ------------------------------------------------
>
>                 Key: NIFI-4491
>                 URL: https://issues.apache.org/jira/browse/NIFI-4491
>             Project: Apache NiFi
>          Issue Type: Improvement
>          Components: Extensions
>            Reporter: Matt Burgess
>            Priority: Major
>
> The main reason CaptureChangeMySQL doesn't leverage the RecordSetWriter API is that those capabilities were being developed in parallel with that processor. Whether a new record-aware processor is better than an improvement to the original is up for discussion; however, it would be a good idea to support the RecordSetWriter API for any CDC (CaptureChangeXYZ) processor.



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