-
Notifications
You must be signed in to change notification settings - Fork 477
Clarify that MOLT Fetch does not migrate sequences #20644
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
Conversation
✅ Deploy Preview for cockroachdb-interactivetutorials-docs canceled.
|
✅ Deploy Preview for cockroachdb-api-docs canceled.
|
Files changed:
|
✅ Netlify Preview
To edit notification comments on pull requests, go to your Netlify project configuration. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looking good! Only one nit, it may be helpful to add something like the below snippet (up to your discretion).
This adds two things: some clarity for users on when/how exactly to create the sequential key manually, and also some specificity by saying after load and replication - since MOLT fetch can run solely data load, replication, or both.
"After loading and replicating data, but before cutover, make sure to update each sequence's current value using setval()
so that new inserts continue from the correct point."
Otherwise, exactly what we needed - thanks!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks clean -- just a few suggestions to bring this in line with our style guide. Let me know if you have questions about any of these.
src/current/_includes/molt/migration-schema-design-practices.md
Outdated
Show resolved
Hide resolved
src/current/_includes/molt/migration-schema-design-practices.md
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
https://cockroachlabs.atlassian.net/browse/DOC-15004
I clarified this in two places:
The first is a bit of relatively low-key guidance here:
/docs/molt/molt-fetch#best-practices
The second is a loud alert here:
/docs/molt/migration-strategy#schema-design-best-practices
(Note that this alert is in an include file so probably shows up in multiple places.)