You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Echo Lee (Jira)" <ji...@apache.org> on 2022/01/06 09:25:00 UTC
[jira] [Commented] (FLINK-19002) Support to only read changelogs of specific database and table for canal-json format
[ https://issues.apache.org/jira/browse/FLINK-19002?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17469791#comment-17469791 ]
Echo Lee commented on FLINK-19002:
----------------------------------
Hi [~jark]
Does this mean that each table corresponds to a Kafka connection? If I want to reuse Kafka connections, are there any other good ideas?
> Support to only read changelogs of specific database and table for canal-json format
> ------------------------------------------------------------------------------------
>
> Key: FLINK-19002
> URL: https://issues.apache.org/jira/browse/FLINK-19002
> Project: Flink
> Issue Type: New Feature
> Components: Formats (JSON, Avro, Parquet, ORC, SequenceFile)
> Reporter: Jark Wu
> Assignee: Jark Wu
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.12.0
>
>
> Usually, users use Canal to synchronize binlog data from various MySQL databases and tables into a single Kafka topic. However, currently, canal-json can't support this case, because it requires the canal data in the topic should be in the same data format.
> This issue propose to introduce a new option "canal-json.database" and "canal-json.table" to filter out the specific data. It would be great to support table list or table pattern in case of all the tables have the same schema.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)