Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[flink-cdc] kafka_sync_database supports table name mapping when prefix and postfix could not fit the need. #4660

Merged
merged 10 commits into from
Dec 10, 2024

Conversation

JackeyLee007
Copy link
Contributor

Purpose

Linked issue: close #4659

kafka_sync_database could map the source table to target table directly, when prefix and postfix is not suitable. Some irregular table names could exists, which could not fitted by only prefix and postfix.

Tests

API and Format

Documentation

Add a new configuration for kafka_sync_database, which named as table_mapping.
For example,

kafka_sync_database 
...
--table_mapping src1=tgt1
--table_mapping src2=tgt2
...
--table_mapping srcn=tgtn

The data in src1, src2, srcn will sink into tgt1, tgt2, tgtn seperately.

Copy link
Contributor

@JingsongLi JingsongLi left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you also update documentation?

@JackeyLee007
Copy link
Contributor Author

Doc provided, but triggered some irrelevant UT failure.

@JingsongLi
Copy link
Contributor

+1

@JingsongLi JingsongLi merged commit 93459f0 into apache:master Dec 10, 2024
12 of 13 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[Feature] kafka_sync_database supports table name mapping when prefix and postfix could not fit the need.
3 participants