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/12/15 15:07:00 UTC

[jira] [Updated] (NIFI-4572) CaptureChangeMySQL does not return database and table info without DistributedMapCache

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

Matt Burgess updated NIFI-4572:
-------------------------------
    Status: Patch Available  (was: In Progress)

> CaptureChangeMySQL does not return database and table info without DistributedMapCache
> --------------------------------------------------------------------------------------
>
>                 Key: NIFI-4572
>                 URL: https://issues.apache.org/jira/browse/NIFI-4572
>             Project: Apache NiFi
>          Issue Type: Improvement
>          Components: Extensions
>            Reporter: Matt Burgess
>            Assignee: Matt Burgess
>            Priority: Major
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> CaptureChangeMySQL will leverage a DistributedMapCache, when enabled, to store database, table, and column information for the configured MySQL instance. This is due to the possibly large amount of information needed to be stored for large tables and large numbers of tables.
> However the database and table information (not columns) is available in the TABLE_MAP event, associated with each MySQL transaction, and it applies to the entire transaction. So this information can be used to populate the database and table fields in the outgoing CDC events, even if the DistributedMapCache is not enabled/configured. This is slightly related to NIFI-3902, although the code locations/paths are likely different.



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