-
Notifications
You must be signed in to change notification settings - Fork 394
mysql clickpipe: binlog faq #3837
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
Conversation
need link for customers being notified their replication is broken due to invalidated binlog
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
3 Skipped Deployments
|
| ### Does the MySQL ClickPipe support Planetscale, Vitess? {#does-the-clickpipe-support-planetscale-vitess} | ||
| Currently, we support only standard MySQL. Since PlanetScale is built on Vitess, integrating with Vitess's VStream API and handling VGtids (Vitess Global Transaction IDs) to track incremental changes is required. This differs from how CDC operates in native MySQL. Adding support for this functionality is being actively worked on. | ||
| ### Does the MySQL ClickPipe support PlanetScale, Vitess, TiDB? {#does-the-clickpipe-support-planetscale-vitess} | ||
| No, these do not support MySQL's binlog API. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I did an evaluation of these alternative's CDC story. Vitess CDC lacks authentication (ie, you connect to grpc endpoint & have complete access). As a result PlanetScale made their own CDC protocol which we would have to implement based on their airbyte connector as a reference implementation. TiDB deprecated support for binlog API, instead implementing TiCDC
This fractured landscape makes implementing a connector for these services less appetizing, to the point that we are not actively working on any of them
|
|
||
| ### Does the MySQL ClickPipe support Planetscale, Vitess? {#does-the-clickpipe-support-planetscale-vitess} | ||
| Currently, we support only standard MySQL. Since PlanetScale is built on Vitess, integrating with Vitess's VStream API and handling VGtids (Vitess Global Transaction IDs) to track incremental changes is required. This differs from how CDC operates in native MySQL. Adding support for this functionality is being actively worked on. | ||
| ### Does the MySQL ClickPipe support PlanetScale, Vitess, or TiDB? {#does-the-clickpipe-support-planetscale-vitess} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
sentence casing this is inconsistent with rest of doc (also I tried appeasing it, maybe TiDB is bothering it?)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@serprex I added MySQL, ClickPipe, PlanetScale, Vitess and TiDB as exceptions and it still wasn't happy :) so we'll ignore it
need link for customers being notified their replication is broken due to invalidated binlog