[SERVER-25955] mongos cannot implicitly create the shard key index when featureCompatibilityVersion is 3.2 Created: 02/Sep/16  Updated: 19/Nov/16  Resolved: 19/Sep/16

Status: Closed
Project: Core Server
Component/s: Querying, Sharding
Affects Version/s: None
Fix Version/s: 3.4.0-rc0

Type: Bug Priority: Major - P3
Reporter: Max Hirschhorn Assignee: Maria van Keulen
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Query 2016-09-19, Query 2016-10-10
Participants:

 Description   

After SERVER-25156 is implemented, specifying the "collation" option in an index specification will require building a v=2 index. However, building a v=2 index is disallowed when the server's featureCompatibilityVersion is 3.2. We should allow mongos to still be able to implicitly create the shard key index on collections with a "simple" default collation by not passing {locale: "simple"} to clusterCreateIndex().



 Comments   
Comment by Githook User [ 16/Sep/16 ]

Author:

{u'username': u'mvankeulen94', u'name': u'Maria van Keulen', u'email': u'maria.vankeulen@mongodb.com'}

Message: SERVER-25955: Only pass simple collation from mongos if necessary

Fixes an issue that prevented mongos from implicitly creating a shard
key index on collections with no default collation when the server's
featureCompatibilityVersion is 3.2.
Branch: master
https://github.com/mongodb/mongo/commit/fd3a4434b891d863437354bf2130885a3a3325a8

Generated at Thu Feb 08 04:10:43 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.