-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Expose record metadata to mongo-cdc #476
Labels
enhancement
New feature or request
Comments
I think you can take a look at the FLIP about the design of the metadadta column. Flink has an good example in the PR[2]. [1] https://cwiki.apache.org/confluence/display/FLINK/FLIP-107%3A+Handling+of+metadata+in+SQL+connectors |
I'm going to support metadata columns for mysql-cdc in the next days, see #249. I think it can be a good example for other connectors. |
Jiabao-Sun
added a commit
to Jiabao-Sun/flink-cdc-connectors
that referenced
this issue
Oct 12, 2021
Jiabao-Sun
added a commit
to Jiabao-Sun/flink-cdc-connectors
that referenced
this issue
Oct 12, 2021
leonardBang
pushed a commit
that referenced
this issue
Nov 3, 2021
Implemented in 65665eb |
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is your feature request related to a problem? Please describe.
It's possible to capture data from multiple mongo databases and collections with the connector, but there is no way to know which database or collection each record came from.
Describe the solution you'd like
The official flink debezium format provides a way to read debezium metadata fields when creating a table DDL (https://nightlies.apache.org/flink/flink-docs-release-1.13/docs/connectors/table/formats/debezium/#available-metadata). Something similar could be done to expose db and collection from the mongo source connector document.
I'm happy to take a stab at this if someone could point me in the right direction.
The text was updated successfully, but these errors were encountered: