[
https://issues.apache.org/jira/browse/NIFI-11279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17700367#comment-17700367
]
ASF subversion and git services commented on NIFI-11279:
--------------------------------------------------------
Commit 9e804fec4ef1ddf0b813b7b25147038b47429001 in nifi's branch
refs/heads/support/nifi-1.x from Matt Burgess
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=9e804fec4e ]
NIFI-11279: Allow event stream processing to continue in CaptureChangeMySQL
after sync issue (#7039)
> CaptureChangeMySQL should not stop processing if event stream is out of sync
> ----------------------------------------------------------------------------
>
> Key: NIFI-11279
> URL: https://issues.apache.org/jira/browse/NIFI-11279
> Project: Apache NiFi
> Issue Type: Bug
> Components: Extensions
> Reporter: Matt Burgess
> Assignee: Matt Burgess
> Priority: Major
> Fix For: 2.0.0, 1.latest, 2.latest
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> Currently if CaptureChangeMySQL gets a BEGIN event while already in a
> transaction or a COMMIT event without being in a transaction, processing of
> the event queue stalls and no data will be emitted. Instead a warning should
> be issued to the user that the event stream may be out of sync, but should
> continue processing binlog events.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
