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.

Sign up for GitHub

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

Jump to bottom

ObjectId plans beyond 2106 #1440

Open

midnight-wonderer opened this issue Jul 5, 2023 · 0 comments

midnight-wonderer commented Jul 5, 2023

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment