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

Posted to issues@nifi.apache.org by "Matt Burgess (Jira)" <ji...@apache.org> on 2023/03/13 17:47:00 UTC

[jira] [Updated] (NIFI-11279) CaptureChangeMySQL should not stop processing if event stream is out of sync

     [ https://issues.apache.org/jira/browse/NIFI-11279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Matt Burgess updated NIFI-11279:
--------------------------------
    Fix Version/s: 1.latest
                   2.latest

> 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: 1.latest, 2.latest
>
>          Time Spent: 10m
>  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)