[DOCS-9787] Clarify that each component of an ObjectID is big endian Created: 17/Jan/17 Updated: 30/Oct/23 Resolved: 25/Nov/19 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | manual, Server |
| Affects Version/s: | None |
| Fix Version/s: | Server_Docs_20231030 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Jeremy Mikola | Assignee: | Andrew Feierabend (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Participants: | |||||||||||||
| Days since reply: | 4 years, 11 weeks, 1 day ago | ||||||||||||
| Epic Link: | DOCSP-1769 | ||||||||||||
| Description |
|
While investigating how Timestamp types are structured and compared for While the BSON spec states that "Each type must be serialized in little-endian format", it's clear that an ObjectID's components must actually be stored in big endian, with the most significant bytes appearing first in the byte sequence. The following pages should be updated to clarify this:
|
| Comments |
| Comment by Githook User [ 26/Nov/19 ] |
|
Author: {'name': 'Andrew Feierabend', 'username': 'andf-mongodb', 'email': 'andrew.feierabend@mongodb.com'}Message: |
| Comment by Githook User [ 26/Nov/19 ] |
|
Author: {'email': 'andrew.feierabend@mongodb.com', 'name': 'Andrew Feierabend', 'username': 'andf-mongodb'}Message: |
| Comment by Githook User [ 26/Nov/19 ] |
|
Author: {'email': 'andrew.feierabend@mongodb.com', 'name': 'Andrew Feierabend', 'username': 'andf-mongodb'}Message: |
| Comment by Githook User [ 26/Nov/19 ] |
|
Author: {'email': 'andrew.feierabend@mongodb.com', 'name': 'Andrew Feierabend', 'username': 'andf-mongodb'}Message: |