Skip to content
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: warn when adding a column family to a table with a running changefeed #76253

Open
HonoreDB opened this issue Feb 8, 2022 · 6 comments
Open
Labels
A-cdc Change Data Capture C-enhancement Solution expected to add code/behavior + preserve backward-compat (pg compat issues are exception) T-sql-foundations SQL Foundations Team (formerly SQL Schema + SQL Sessions)

Comments

@HonoreDB
Copy link
Contributor

HonoreDB commented Feb 8, 2022

With links to docs.

Jira issue: CRDB-13047

Epic CRDB-31637

@HonoreDB HonoreDB added C-enhancement Solution expected to add code/behavior + preserve backward-compat (pg compat issues are exception) T-cdc labels Feb 8, 2022
@HonoreDB HonoreDB self-assigned this Feb 8, 2022
@blathers-crl
Copy link

blathers-crl bot commented Feb 8, 2022

cc @cockroachdb/cdc

@blathers-crl blathers-crl bot added the A-cdc Change Data Capture label Feb 8, 2022
@miretskiy
Copy link
Contributor

What's the motivation here? Not sure how this would play w/ tying jobs system into schema changes...

@ajwerner
Copy link
Contributor

ajwerner commented Feb 8, 2022

Regarding this, one thing I've been thinking is it's now very easy to breaking the rangefeed.enabled setting down per table (#70614, #73045)

I wonder if, in some future, we'd want to go an make users mark tables as explicitly having changefeeds enabled. Then we could warn if adding a column family to a table which has changefeeds enabled. cc @amruss

@miretskiy miretskiy added the T-sql-foundations SQL Foundations Team (formerly SQL Schema + SQL Sessions) label Sep 18, 2023
@miretskiy
Copy link
Contributor

Adding this issue for sql-foundations triage.
Schema changes could be disruptive to running changefeeds because some of those changes
trigger backfills. This often causes "surprises" that our customers would like to avoid (including
overloading their downstream clusters, causing significant latency spikes, etc).

We would like to have a guard-rail to ensure that when schema change is attempted, the user
will either get a warning, or even an error message (similar to how "schema_locked" table parameter operates)
to get an explicit confirmation.

@rafiss
Copy link
Collaborator

rafiss commented Sep 19, 2023

@dikshant will determine how to prioritize this.

@dikshant
Copy link

dikshant commented Jan 5, 2024

Internal discussion here: https://cockroachlabs.slack.com/archives/C9TGBJB44/p1695330349551529
We won't be investing in this right now since there are other priorities for schema: eg finishing declarative schema changer.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-cdc Change Data Capture C-enhancement Solution expected to add code/behavior + preserve backward-compat (pg compat issues are exception) T-sql-foundations SQL Foundations Team (formerly SQL Schema + SQL Sessions)
Projects
No open projects
Status: Triage
Development

No branches or pull requests

5 participants