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 2022/11/22 19:11:00 UTC
[jira] [Updated] (NIFI-6428) CaptureChangeMySQL throws IOException with BIGIN event due to lingering 'inTransaction' instance variable
[ https://issues.apache.org/jira/browse/NIFI-6428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Matt Burgess updated NIFI-6428:
-------------------------------
Status: Patch Available (was: Open)
> CaptureChangeMySQL throws IOException with BIGIN 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
> Time Spent: 1h 50m
> 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)