Hello Chris and MongoDB community,
I realize this is an old post, but I am curious about the 32-bit time_t part of BSON Timestamp… Is it a signed or unsigned field? I ask because if it is signed, it will rollover on Jan 19, 2038 (due to the Y2038 issue). If it is unsigned, then it will not rollover until the year 2106. I also realize that the use of BSON Timestamp is intended for internal use only, but my concern is that there could be internal Y2038 issues, or stray uses of BSON Timestamp in applications that may be susceptible to Y2038 if the time_t field in BSON Timestamp is signed.
Thanks,
-John