-
Type:
Improvement
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Affects Version/s: 8.3.0-rc0
-
Component/s: Catalog
-
Catalog and Routing
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Consider the following oplog entry:
const createCollectionOplogEntry = {
op: "c",
ns: "test.$cmd",
o: {
create: "ts",
clusteredIndex: true,
timeseries:
,
},
};
If we run the applyOps command on a primary with this entry, we will successfully create a collection that has time-series options but does not have a corresponding buckets collection.
Interestingly also, it does not appear that this collection appears when running the listCommand command.
Using rawData, it appears that the collection is still bucketing data and is functionally a time-series collection. So essentially it seems that this creates a viewless time-series collection, without having the feature flag for this feature enabled
- is related to
-
SERVER-111180 applyOps command creates extra time-series index
-
- Closed
-