[
https://issues.apache.org/jira/browse/NIFI-4572?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17649398#comment-17649398
]
ASF subversion and git services commented on NIFI-4572:
-------------------------------------------------------
Commit 2a88980024d79f89abb28cc0b13f9cac753d7a0f in nifi's branch
refs/heads/main from Matt Burgess
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=2a88980024 ]
NIFI-4572: Include database and table names in CaptureChangeMySQL events even
when cache is not configured
This closes #6786.
Signed-off-by: Tamas Palfy <[email protected]>
> 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)
