As of FCV 5.0, all Database and Collection entries now contain a Timestamp entry, which takes the responsibilities of the former Epoch. As a result of this, we can stop relying on Epoch internally in the code and in 6.1 we can throw out the Epoch field entirely.
- causes
-
SERVER-64199 Routing performance benchmarks use default Timestamp for the collection
-
- Closed
-