[
https://issues.apache.org/jira/browse/NIFI-4491?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17611188#comment-17611188
]
David Handermann commented on NIFI-4491:
----------------------------------------
Commenting on this issue for future reference, it seems best to create a new
record-oriented Processor as opposed to implemented record-oriented processing
in CaptureChangeMySQL. Handling large numbers of binary log events is not
optimal for framework processing, so a new record-oriented version could
provide a recommend way forward that would enable deprecation of the current
Processor for eventual removal.
> 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)
