search

risingwavelabs / risingwave

Best-in-class stream processing, analytics, and management. Perform continuous analytics, or build event-driven applications, real-time ETL pipelines, and feature stores in minutes. Unified streaming and batch. PostgreSQL compatible.
https://go.risingwave.com/slack
Apache License 2.0
6.88k stars 569 forks source link

support direct CDC for Oracle、SQLserver #14024

Open yanggengwei opened 9 months ago

yanggengwei commented 9 months ago

Is your feature request related to a problem? Please describe.

No response

Describe the solution you'd like

No response

Describe alternatives you've considered

No response

Additional context

No response

neverchanje commented 9 months ago

Thanks for bringing up this request!

Although Oracle and SQLServer are not yet supported, I'd suggest using Debezium and Kafka as the bridge. The stack of Debezium, SQLServer, Kafka and RisingWave has been tested here: https://github.com/risingwavelabs/risingwave/tree/main/integration_tests/debezium-sqlserver A direct solution is in our roadmap. But it won't be available very soon.

whmnoe4j commented 4 months ago

Thanks for bringing up this request!

Although Oracle and SQLServer are not yet supported, I'd suggest using Debezium and Kafka as the bridge. The stack of Debezium, SQLServer, Kafka and RisingWave has been tested here: https://github.com/risingwavelabs/risingwave/tree/main/integration_tests/debezium-sqlserver A direct solution is in our roadmap. But it won't be available very soon.

Do you have a time plan to complete this function？ We really need this feature！

neverchanje commented 4 months ago

Hi, @whmnoe4j We've already been working on the direct SqlServer CDC for the enterprise edition. We estimate that it could be released at around 1.11, i.e, the version in 1~2 months later.

Before it comes out, we highly recommend you to use Debezium+Kafka as the middleware for CDC, which will be supported for all RisingWave editions.

github-actions[bot] commented 2 months ago

This issue has been open for 60 days with no activity.

If you think it is still relevant today, and needs to be done in the near future, you can comment to update the status, or just manually remove the no-issue-activity label.

You can also confidently close this issue as not planned to keep our backlog clean. Don't worry if you think the issue is still valuable to continue in the future. It's searchable and can be reopened when it's time. 😄