Skip to content
This repository was archived by the owner on May 1, 2025. It is now read-only.

Conversation

@ltran-mdb2
Copy link
Collaborator

DESCRIPTION

adding sorting and uuids information to mongosync page

STAGING

https://preview-mongodbltranmdb2.gatsbyjs.io/cluster-sync/DOCSP-29155/reference/mongosync/#uuids

JIRA

https://jira.mongodb.org/browse/DOCSP-29155

BUILD LOG

https://workerpool-boxgs.mongodbstitch.com/pages/job.html?collName=queue&jobId=6580ab867a5cb5fef55f4e19

Self-Review Checklist

  • Is this free of any warnings or errors in the RST?
  • Is this free of spelling errors?
  • Is this free of grammatical errors?
  • Is this free of staging / rendering issues?
  • Are all the links working?

External Review Requirements

What's expected of an external reviewer?

Copy link
Collaborator

@MongoCaleb MongoCaleb left a comment

Choose a reason for hiding this comment

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

A few suggestions.

Sorting
~~~~~~~

``mongosync`` creates a new natural (without any sort method specified)
Copy link
Collaborator

Choose a reason for hiding this comment

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

I think it reads better to say "creates a new natural order (without any sort method specified) on the ..."

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Done!

``mongosync`` creates a new natural (without any sort method specified)
order on the destination cluster. If applications depend on document
order without a defined sort method, they may require additional updating to
work with a migrated cluster.
Copy link
Collaborator

Choose a reason for hiding this comment

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

I think this can be cleaned up a bit and also be more specific about what needs to be updated. Perhaps:

If applications depend on document order, but don't have a defined sort method, they may need to be updated to specify the expected sort order before they will work properly with the migrated cluster.

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Done!

UUIDs
~~~~~

``mongosync`` creates new universally unique identifiers (UUIDs) for
Copy link
Collaborator

Choose a reason for hiding this comment

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

I don't know if we should use this:
:abbr:`UUIDs (universally unique identifiers)`

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Done! (I was not aware of this markup so thank you so much for pointing it out!)

``mongosync`` creates new universally unique identifiers (UUIDs) for
collections on the destination cluster. There is no relationship between
UUIDs on the source cluster and the destination cluster. If applications
contain hard-coded collection UUIDs (which MongoDB does not recommend),
Copy link
Collaborator

Choose a reason for hiding this comment

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

Are they "collection UUIDs" or document UUIDs within a collection? If the latter, I suggest just dropping the word "collection".

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Done!

@ltran-mdb2
Copy link
Collaborator Author

Thanks for your feedback @MongoCaleb ! Could you take another look when you get a chance?

Copy link
Collaborator

@MongoCaleb MongoCaleb left a comment

Choose a reason for hiding this comment

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

I'm LGTMing, but there's one important question to check on.

between UUIDs on the source cluster and the destination cluster. If
applications contain hard-coded UUIDs (which MongoDB does not
recommend), you may need to update the application's UUIDs before the
application works properly with a migrated cluster.
Copy link
Collaborator

Choose a reason for hiding this comment

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

One last comment. Can you actually change the UUIDs? I would be surprised if this were the case.

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Checked in with Alex Komyagin who said the "The developer would need to get the new UUID's from the new cluster or update the app not to rely on UUIDs" so I changed the phrasing accordingly

Copy link
Contributor

@FGasper FGasper left a comment

Choose a reason for hiding this comment

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

The gist of what’s here is accurate. I’ve left a couple technical-nit comments, and one grammatical nit. See what you think.

Thank you!

Comment on lines 302 to 303
``mongosync`` creates new :abbr:`UUIDs (universally unique identifiers)`
for collections on the destination cluster. There is no relationship
Copy link
Contributor

Choose a reason for hiding this comment

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

mongosync doesn’t “create UUIDs” per se; rather, it creates collections, which have UUIDs.

Suggested change
``mongosync`` creates new :abbr:`UUIDs (universally unique identifiers)`
for collections on the destination cluster. There is no relationship
The collections that ``mongosync`` creates on the destination cluster
have new :abbr:`UUIDs (universally unique identifiers)`. There is no relationship

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Done!

Comment on lines 315 to 316
update the application to specify the expected sort order before the
application works properly with the migrated cluster.
Copy link
Contributor

Choose a reason for hiding this comment

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

Just a grammatical nit:

Suggested change
update the application to specify the expected sort order before the
application works properly with the migrated cluster.
update those applications to specify the expected sort order before the
applications work properly with the migrated cluster.

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Done!

Comment on lines 312 to 313
``mongosync`` creates a new natural order (without any sort method
specified) on the destination cluster. If applications depend on
Copy link
Contributor

Choose a reason for hiding this comment

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

mongosync doesn’t “create an order”; rather, the order in which it inserts documents is undefined.

Suggested change
``mongosync`` creates a new natural order (without any sort method
specified) on the destination cluster. If applications depend on
``mongosync`` inserts documents on the destination cluster in an undefined order.
Thus, natural sort order is not preserved from the source to the destination. If applications
depend on

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Done!

@ltran-mdb2
Copy link
Collaborator Author

Thanks for your feedback @FGasper ! Could you take another look at this when you get a chance?

Copy link
Contributor

@FGasper FGasper left a comment

Choose a reason for hiding this comment

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

LGTM. Thanks!

@sarah-olson-mongodb sarah-olson-mongodb merged commit 4027ad4 into mongodb:master Jan 9, 2024
ltran-mdb2 added a commit to ltran-mdb2/docs-cluster-to-cluster-sync that referenced this pull request Jan 10, 2024
* DOCSP-29155 adding behavior info to mongosync

* DOCSP-29155 adding sorting and uuids to mongosync page

* DOCSP-29155 adding sorting and uuids to mongosync page

* DOCSP-29155 copy edits

* DOCSP-29155 copy edit

* DOCSP-29155 tech edits

* DOCSP-29155 tech edits

* DOCSP-29155 tech edits

* DOCSP-29155 tech edits

* DOCSP-29155 tech edit
ltran-mdb2 added a commit to ltran-mdb2/docs-cluster-to-cluster-sync that referenced this pull request Jan 11, 2024
* DOCSP-29155 adding behavior info to mongosync

* DOCSP-29155 adding sorting and uuids to mongosync page

* DOCSP-29155 adding sorting and uuids to mongosync page

* DOCSP-29155 copy edits

* DOCSP-29155 copy edit

* DOCSP-29155 tech edits

* DOCSP-29155 tech edits

* DOCSP-29155 tech edits

* DOCSP-29155 tech edits

* DOCSP-29155 tech edit
sarah-olson-mongodb pushed a commit that referenced this pull request Jan 11, 2024
* DOCSP-29155 adding behavior info to mongosync

* DOCSP-29155 adding sorting and uuids to mongosync page

* DOCSP-29155 adding sorting and uuids to mongosync page

* DOCSP-29155 copy edits

* DOCSP-29155 copy edit

* DOCSP-29155 tech edits

* DOCSP-29155 tech edits

* DOCSP-29155 tech edits

* DOCSP-29155 tech edits

* DOCSP-29155 tech edit
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants