summaryrefslogtreecommitdiff
path: root/jstests/sharding/index_and_collection_option_propagation.js
diff options
context:
space:
mode:
Diffstat (limited to 'jstests/sharding/index_and_collection_option_propagation.js')
-rw-r--r--jstests/sharding/index_and_collection_option_propagation.js5
1 files changed, 1 insertions, 4 deletions
diff --git a/jstests/sharding/index_and_collection_option_propagation.js b/jstests/sharding/index_and_collection_option_propagation.js
index e24d8c9f064..32d9a1809b2 100644
--- a/jstests/sharding/index_and_collection_option_propagation.js
+++ b/jstests/sharding/index_and_collection_option_propagation.js
@@ -2,10 +2,7 @@
* Mongos has special targeting behavior for createIndex, reIndex, dropIndex, and collMod:
*
* - If called on an unsharded collection, the request is routed only to the primary shard.
- * - If called on a sharded collection, in v4.4 the request is broadcast to shards with chunks;
- * in previous versions, the request is broadcast to all shards but NamespaceNotFound and
- * CannotImplicitlyCreateCollection errors do not lead to command failure (though these errors
- * are reported in the 'raw' shard responses) as long as at least one shard returns success.
+ * - If called on a sharded collection, the request is broadcast to shards with chunks.
*
* This test verifies this behavior.
*/