-
Type:
Bug
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Affects Version/s: 8.1.0-rc0
-
Component/s: None
-
None
-
Query Optimization
-
ALL
-
-
200
If I insert a Timestamp(0,0) value in some collection, the following things happen:
1. If $$CLUSTER_TIME did not exist previously because it is not a replica set or a sharded cluster, it now exists.
2. The value of $CLUSTER_TIME seems stuck to the time of the latest insertion of Timestamp(0,0) , until another such insertion occurs.
- is related to
-
SERVER-100714 Do not use Timestamp(0,0) in CBR tests
-
- Closed
-
- related to
-
SERVER-88750 Add "bypassEmptyTsReplacement" param to insert, update, findAndModify, and bulkWrite
-
- Closed
-