mongodb / mongodb/specifications
ObjectId plans beyond 2106
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 409
- Forks
- 248
- Avg merge
- 3d 9h
- Merged PRs (30d)
- 7
Description
Hi, we are probably dead by then, but I wonder what is the plan beyond 2106?
As you may know, ObjectId will overflow on February 7, 2106; there are a couple of ways forward then.
- extend ObjectId by 1 byte
- do nothing, using the current specification, and let it overflow into 1970.
These impact how we design the schema now, as we can either:
- simply store ObjectId if the plan is to extend the timestamp portion of ObjectId
- store ObjectId and time as separate fields, and never use ObjectId as time
What do you say?
P.S. BTW, the specification is currently incorrect; the ObjectId will overflow in Feb, not in Jan.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the ObjectId specification at source/objectid.rst, linked in the issue, and review its timestamp-field overflow statement. Done would be an agreed plan for behavior beyond 2106 and a corrected specification date if needed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- mongodb
- Domain
- databases
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100