Skip to content

Conversation

bsanchez-the-roach
Copy link
Contributor

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.)

@netlify
Copy link

netlify bot commented Oct 16, 2025

Deploy Preview for cockroachdb-interactivetutorials-docs canceled.

Name Link
🔨 Latest commit 663cb13
🔍 Latest deploy log https://app.netlify.com/projects/cockroachdb-interactivetutorials-docs/deploys/68f7f8ad6d01bd0008fcb75a

@netlify
Copy link

netlify bot commented Oct 16, 2025

Deploy Preview for cockroachdb-api-docs canceled.

Name Link
🔨 Latest commit 663cb13
🔍 Latest deploy log https://app.netlify.com/projects/cockroachdb-api-docs/deploys/68f7f8ad618589000852c149

@github-actions
Copy link

Files changed:

@netlify
Copy link

netlify bot commented Oct 16, 2025

Netlify Preview

Name Link
🔨 Latest commit 663cb13
🔍 Latest deploy log https://app.netlify.com/projects/cockroachdb-docs/deploys/68f7f8adcf45520008031fb6
😎 Deploy Preview https://deploy-preview-20644--cockroachdb-docs.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

Copy link

@tuansydau tuansydau left a 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!

Copy link
Contributor

@taroface taroface left a 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.

Copy link
Contributor

@taroface taroface left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

@bsanchez-the-roach bsanchez-the-roach merged commit 932f076 into main Oct 21, 2025
5 checks passed
@bsanchez-the-roach bsanchez-the-roach deleted the DOC-15004 branch October 21, 2025 21:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants