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.

Sign up for GitHub

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

Jump to bottom

changefeedccl: persist changefeeds across backup/restore #73434

Closed
amruss opened this issue Dec 3, 2021 · 2 comments
Closed

changefeedccl: persist changefeeds across backup/restore #73434

amruss opened this issue Dec 3, 2021 · 2 comments
Labels
C-enhancement Solution expected to add code/behavior + preserve backward-compat (pg compat issues are exception) docs-done docs-known-limitation T-cdc

Comments

@amruss
Copy link
Contributor

amruss commented Dec 3, 2021 •
edited by cockroach-jira-scripts
Loading

When a user restores a database from a backup, information about running changefeeds is lost. We should persist changefeeds across databases that are restored, with the clear communication to users the changefeed data would be bounded by similar RPO limitations as backup data is.

Epic CRDB-11782

Jira issue: CRDB-11588
@amruss amruss added the C-enhancement Solution expected to add code/behavior + preserve backward-compat (pg compat issues are exception) label Dec 3, 2021
@blathers-crl blathers-crl bot added the T-cdc label Dec 3, 2021
@blathers-crl
Copy link

blathers-crl bot commented Dec 3, 2021

cc @cockroachdb/cdc

@amruss amruss mentioned this issue Dec 3, 2021
Closed
@exalate-issue-sync exalate-issue-sync bot mentioned this issue Dec 3, 2021
Closed
@miretskiy
Copy link
Contributor

I don't think it's a good idea at any rate.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
C-enhancement Solution expected to add code/behavior + preserve backward-compat (pg compat issues are exception) docs-done docs-known-limitation T-cdc
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@amruss @miretskiy