You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Pierre Villard (Jira)" <ji...@apache.org> on 2020/09/17 10:30:00 UTC
[jira] [Updated] (NIFI-5583) Make Change Data Capture (CDC)
processor for MySQL refer to GTID
[ https://issues.apache.org/jira/browse/NIFI-5583?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Pierre Villard updated NIFI-5583:
---------------------------------
Fix Version/s: 1.13.0
Resolution: Fixed
Status: Resolved (was: Patch Available)
> Make Change Data Capture (CDC) processor for MySQL refer to GTID
> ----------------------------------------------------------------
>
> Key: NIFI-5583
> URL: https://issues.apache.org/jira/browse/NIFI-5583
> Project: Apache NiFi
> Issue Type: New Feature
> Components: Extensions
> Affects Versions: 1.7.1
> Reporter: Yoshiaki Takahashi
> Assignee: Yoshiaki Takahashi
> Priority: Major
> Fix For: 1.13.0
>
> Time Spent: 2h 50m
> Remaining Estimate: 0h
>
> When connecting to a MySQL cluster consisting of multiple hosts, existing CDC processor can not automatically switch to other host when the connected host goes down.
> The reason is that file names and positions of binary log may be different for each host in the same cluster.
> In such a case it is impossible to continue reading files from the same position.
> In order to continue reading in such cases, a processor referring to the GTID (Global Transaction ID) is necessary.
> GTID is ID that uniquely identifies a transaction, and it is recorded in binary log of MySQL.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)