[jira] [Updated] (NIFI-6428) CaptureChangeMySQL throws IOException with BEGIN event due to lingering 'inTransaction' instance variable

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

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

Matt Burgess updated NIFI-6428:
-------------------------------
    Summary: CaptureChangeMySQL throws IOException with BEGIN event due to lingering 'inTransaction' instance variable  (was: CaptureChangeMySQL throws IOException with BIGIN event due to lingering 'inTransaction' instance variable)

> CaptureChangeMySQL throws IOException with BEGIN event due to lingering 'inTransaction' instance variable
> ---------------------------------------------------------------------------------------------------------
>
>                 Key: NIFI-6428
>                 URL: https://issues.apache.org/jira/browse/NIFI-6428
>             Project: Apache NiFi
>          Issue Type: Bug
>            Reporter: Koji Kawamura
>            Priority: Major
>             Fix For: 1.20.0, 1.19.1
>
>          Time Spent: 2h 10m
>  Remaining Estimate: 0h
>
> Because of not clearing 'inTransaction' instance variable when the processor stops, when a user clears processor state and restart it with a specific initial binlog position, then if BEGIN event is received, the processor throws an IOException.
> The processor should reset 'inTransaction' to false, and also other instance variables when it start with an empty processor state.
> The issue was reported at NiFi user ML.
> [https://mail-archives.apache.org/mod_mbox/nifi-users/201907.mbox/%3C2019070919385393266224%40geekplus.com.cn%3E]



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