-
Notifications
You must be signed in to change notification settings - Fork 455
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
CDC: Add GitHub Tracking Issues to Limitations #12295
Comments
Kathryn Hancox (kathancox) commented:
|
Abbey Russell (amruss) commented: Changefeeds do not share internal buffers, so each running changefeed will increase total memory usage: this is a consideration, not something that will change Many DDL queries (including {{TRUNCATE}} and {{DROP TABLE}}) will cause errors on a changefeed watching the affected tables: I would put this is consideration for now. I don’t think it’s something we can fix and we certainly have no plans to try. Changefeeds cannot be backed up or restored: This is probably a limitation, we could and probably eventually will do something about this - needs github issue Partial or intermittent sink unavailability may impact changefeed stability; however, ordering guarantees will still hold for as long as a changefeed remains active: This is a consideration you should plan/configure against. Changefeeds cannot be altered: limitation, something we are planning to address. I think the issue is fine. Additional target options will be added, including partitions: I think this is a limitation if we rephrase to “target options limited to tables currently”. Needs issue. When an {{IMPORT INTO}} statement is run, changefeed jobs targeting that table will fail: I’d put this in considerations since I don’t think we’re going to fix this. Using a cloud storage sink only works with {{JSON}} and emits newline-delimited json files: Definitely limitation. Hmm I don’t know about that issue. I think it implies that Apache Parque is the first format we’ll support after JSON, which I don’t want to commit to. Webhook sinks only support HTTPS. Use the {{insecure_tls_skip_verify}} parameter when testing to disable certificate verification; however, this still requires HTTPS and certificates: Hmm definitely a limitation. But we also made a deliberate choice to only support https right now. Probably should just file and issue and backlog it. Currently, webhook sinks only have support for emitting {{JSON}}: Limitation, though maybe should just have the same github issue as cloud storage. There is no concurrency configurability for webhook sinks: Limitation, I think we already have an issue for this I’ll look. Ent changefeeds are currently disabled for serverless clusters. Core changefeeds are enabled: limitation we’re working on right now 🙂. I’ll find an appropriate issue |
Abbey Russell (amruss) commented: Changefeeds cannot be altered: cockroachdb/cockroach#28668 Additional target options will be added, including partitions: cockroachdb/cockroach#73435 Using a cloud storage sink only works with {{JSON}} and emits newline-delimited json files: cockroachdb/cockroach#73432 Webhook sinks only support HTTPS: cockroachdb/cockroach#73431 Currently, webhook sinks only have support for emitting {{JSON: https://github.com/cockroachdb/cockroach/issues/73432}}: cockroachdb/cockroach#73432 There is no concurrency configurability for webhook sinks: cockroachdb/cockroach#73430 Ent changefeeds are currently disabled for serverless clusters. Core changefeeds are enabled: cockroachdb/cockroach#73429 |
Kathryn Hancox (kathancox) commented:
Currently the CDC limitations do not have any GitHub Tracking Issues as per the style for our Known Limitations.
This issue is to add Tracking issues to them where possible. Where there isn't a tracking issue and we're not planning to work on the product in this area, I propose moving to a Considerations section... similar to here on the IMPORT INTO page.
Jira Issue: DOC-1112
The text was updated successfully, but these errors were encountered: