-
Notifications
You must be signed in to change notification settings - Fork 3.8k
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
backupccl: backup/restore does not handle comments #44396
Comments
cc @hueypark FYI |
@jseldess do you still use the "docs-known-limitation" label? Otherwise what's the current process to report and document known limitations? |
On the bright side, I think the new "full-cluster backup" in 20.1 will preserve comments just fine (indeed, there is a test of this in the current PR h/t @pbardea), but backing up individual tables or databases currently will not right now. Doing so will require adding some special-purpose code to BACKUP to gather the applicable rows from system.comments for the set of IDs being backed up, and then code in RESTORE to re-key those rows to the new IDs and insert them into the existing system.comments on the RESTOREing cluster. |
@knz, yes, we use that label to identify new known limitations to document for a GA release. Once we have in the docs, we add |
Nice catch @knz |
@dt caught it. I merely filed the issue. |
Documented in cockroachdb/docs#7118. |
@knz I think we already resolved this issue(#43152) and merged it to 20.1 branch. Am I wrong? |
yes, correct. thanks for noticing! |
@jseldess We should also reflect on the changes in the 20.1 documentation. |
Hm, unfortunately I don't think that #43152 quite resolves this issue. A BACKUP of a table or database will not by default include |
Interesting. Let me look a little further. |
Fixes cockroachdb#44396 Release note: Enterprise `BACKUP` does capture database, table,column and index comments
We are considering changing the format we store backup metadata as a project for our 21.2 release. This new format would unlock the ability to store larger types of metadata egs: comments, stats and so we should off on addressing this issue until then! |
We have marked this issue as stale because it has been inactive for |
Since 19.2 CockroachDB supports the COMMENT statement to decorate database, tables and columns. We plan to extend it for sequences, views, indexes as well (#44135).
Comments are stored in a separate table
system.comments
.cockroach dump
in the CLI handles this by emitting theCOMMENT
statements alongsideCREATE
in the output.However BACKUP does not capture the comments and they are thus not restorable.
Jira issue: CRDB-5231
The text was updated successfully, but these errors were encountered: