DOC-12453 restore different storage engines (and fixes to Auto-remove Collections) #3680
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
* Added statement that the * Heavily edited the Restore Backups section to bring it up to standards. * Corrected several errors in the documentation. * Had to do more editing to earlier parts of the topic to reduce the number of Vale errors so I could get my sections written. There were so many issues in the page before my updates that VS Code stopped checking.
… fix, but I want to wrap this up.
ggray-cb
requested review from
bfavini,
cbvipulgupta,
hyunjuV,
mattyhall and
safianalicb
cbvipulgupta
approved these changes
Sep 4, 2024
RayOffiah
pushed a commit
that referenced
this pull request
Nov 2, 2024
… Collections) (#3680) * Current progress, mainly on updating the restore backup. * In progress checkin: * Added statement that the * Heavily edited the Restore Backups section to bring it up to standards. * Corrected several errors in the documentation. * Had to do more editing to earlier parts of the topic to reduce the number of Vale errors so I could get my sections written. There were so many issues in the page before my updates that VS Code stopped checking. * A few more low-hanging-fruit fixes to make Vale happy. Plenty more to fix, but I want to wrap this up.
simon-dew
pushed a commit
that referenced
this pull request
Nov 12, 2024
… Collections) (#3680) * Current progress, mainly on updating the restore backup. * In progress checkin: * Added statement that the * Heavily edited the Restore Backups section to bring it up to standards. * Corrected several errors in the documentation. * Had to do more editing to earlier parts of the topic to reduce the number of Vale errors so I could get my sections written. There were so many issues in the page before my updates that VS Code stopped checking. * A few more low-hanging-fruit fixes to make Vale happy. Plenty more to fix, but I want to wrap this up.
simon-dew
pushed a commit
that referenced
this pull request
Nov 12, 2024
… Collections) (#3680) * Current progress, mainly on updating the restore backup. * In progress checkin: * Added statement that the * Heavily edited the Restore Backups section to bring it up to standards. * Corrected several errors in the documentation. * Had to do more editing to earlier parts of the topic to reduce the number of Vale errors so I could get my sections written. There were so many issues in the page before my updates that VS Code stopped checking. * A few more low-hanging-fruit fixes to make Vale happy. Plenty more to fix, but I want to wrap this up.
RayOffiah
pushed a commit
that referenced
this pull request
Dec 9, 2024
… Collections) (#3680) * Current progress, mainly on updating the restore backup. * In progress checkin: * Added statement that the * Heavily edited the Restore Backups section to bring it up to standards. * Corrected several errors in the documentation. * Had to do more editing to earlier parts of the topic to reduce the number of Vale errors so I could get my sections written. There were so many issues in the page before my updates that VS Code stopped checking. * A few more low-hanging-fruit fixes to make Vale happy. Plenty more to fix, but I want to wrap this up.
RayOffiah
pushed a commit
that referenced
this pull request
Dec 9, 2024
… Collections) (#3680) * Current progress, mainly on updating the restore backup. * In progress checkin: * Added statement that the * Heavily edited the Restore Backups section to bring it up to standards. * Corrected several errors in the documentation. * Had to do more editing to earlier parts of the topic to reduce the number of Vale errors so I could get my sections written. There were so many issues in the page before my updates that VS Code stopped checking. * A few more low-hanging-fruit fixes to make Vale happy. Plenty more to fix, but I want to wrap this up.
rao-shwe
pushed a commit
that referenced
this pull request
Dec 10, 2024
… Collections) (#3680) * Current progress, mainly on updating the restore backup. * In progress checkin: * Added statement that the * Heavily edited the Restore Backups section to bring it up to standards. * Corrected several errors in the documentation. * Had to do more editing to earlier parts of the topic to reduce the number of Vale errors so I could get my sections written. There were so many issues in the page before my updates that VS Code stopped checking. * A few more low-hanging-fruit fixes to make Vale happy. Plenty more to fix, but I want to wrap this up.
rao-shwe
pushed a commit
that referenced
this pull request
Dec 10, 2024
… Collections) (#3680) * Current progress, mainly on updating the restore backup. * In progress checkin: * Added statement that the * Heavily edited the Restore Backups section to bring it up to standards. * Corrected several errors in the documentation. * Had to do more editing to earlier parts of the topic to reduce the number of Vale errors so I could get my sections written. There were so many issues in the page before my updates that VS Code stopped checking. * A few more low-hanging-fruit fixes to make Vale happy. Plenty more to fix, but I want to wrap this up.
simon-dew
pushed a commit
that referenced
this pull request
Dec 10, 2024
… Collections) (#3680) * Current progress, mainly on updating the restore backup. * In progress checkin: * Added statement that the * Heavily edited the Restore Backups section to bring it up to standards. * Corrected several errors in the documentation. * Had to do more editing to earlier parts of the topic to reduce the number of Vale errors so I could get my sections written. There were so many issues in the page before my updates that VS Code stopped checking. * A few more low-hanging-fruit fixes to make Vale happy. Plenty more to fix, but I want to wrap this up.
simon-dew
pushed a commit
that referenced
this pull request
Dec 10, 2024
… Collections) (#3680) * Current progress, mainly on updating the restore backup. * In progress checkin: * Added statement that the * Heavily edited the Restore Backups section to bring it up to standards. * Corrected several errors in the documentation. * Had to do more editing to earlier parts of the topic to reduce the number of Vale errors so I could get my sections written. There were so many issues in the page before my updates that VS Code stopped checking. * A few more low-hanging-fruit fixes to make Vale happy. Plenty more to fix, but I want to wrap this up.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Main rational behind this change is to explicitly state that you can restore a backup taken from a bucket using one storage backend (i.e. Couchstore) and restore it to a bucket using another backend (i.e. Magma). This is to hopefully get the AI to respond correctly when asked about this.
For a preview of the changes, see:
Because I was there, I took some time to review the restore section of the documentation and experimenting with the backup system. Then I fixed a bunch more stuff:
Also, I found that VS Code is limited to reporting 1000 or so issues at a time. This limits our text linting tool (Vale). This page has more than that many standards violations in it, so I fixed enough issues in other sections of the page to bring the issue count down to where Vale could check my edits. There's a lot more to do in this page (and it probably needs to be restructured into several separate pages). I've created DOC-12508 to track further fixes for this page.