|
josef.ahmad
For what it's worth, remove does work, just not on a buckets collection it seems.
I made the following changes to confirm this is a non-issue for other types of clustered collections
diff --git a/jstests/core/clustered_index_creation.js b/jstests/core/clustered_index_creation.js
|
index df98c629be..6d62c62692 100644
|
--- a/jstests/core/clustered_index_creation.js
|
+++ b/jstests/core/clustered_index_creation.js
|
@@ -48,6 +48,12 @@ const validateListCollections = function(db, collName, creationOptions) {
|
*/
|
const runSuccessfulCreate = function(db, coll, creationOptions) {
|
assert.commandWorked(db.createCollection(coll.getName(), creationOptions));
|
+
|
+ assert.commandWorked(coll.insert({_id: 1}));
|
+ assert.eq(coll.find({_id: 1}).itcount(), 1);
|
+ assert.commandWorked(coll.remove({_id: 1}));
|
+ assert.eq(coll.find({_id: 1}).itcount(), 0);
|
+
|
validateListCollections(testDB, coll.getName(), creationOptions);
|
coll.drop();
|
};
|
I think the question is- do we want to restrict users from inserting into system.buckets collections altogether/ is there a ticket for this?
Otherwise, this ticket can be changed to specify the issue is only for timeseries / buckets collections
|