Debezium sink connector for MongoDB [DBZ-8339]
- Dominant language
- HTML
- Stars
- 6
- Forks
- 8
- Avg merge
- 2d 19h
- Merged PRs (30d)
- 1
Description
Migrated from [DBZ-8339](https://issues.redhat.com/browse/DBZ-8339)
h1. Feature request or enhancement
For feature requests or enhancements, provide this information, please:
h2. Which use case/requirement will be addressed by the proposed feature?
Customer is trying extract a relational database, and take it to a non-relational database.
The flow is as follows:
1) Origin (PostgreSQL DB)
2) Extraction( Debezium)
3) Kafka
4) Target (MongoDB and Redis)
h2. Implementation ideas (optional)
discussed with engineering team. Please find below answer
Neither Mongo nor Redis is a JDBC compatible database (JDBC is a RDMS connection "standard" for java) so unfortunately that will not work.
Currently RedHat only support MongoDB as a source connector downstream. Sink connector for MongoDB is currently under development in our upstream.
Contributor guide
Research direction
No repository files, tests, or entry points are identified in the issue. Start by reviewing the proposed PostgreSQL-to-Kafka-to-MongoDB flow and the existing upstream connector work, then define the supported sink behavior and validation needed for the MongoDB target.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kafka, mongodb, postgresql, redis
- Domain
- data-engineering, databases
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100