[SERVER-62811] Allow special index types on cluster keys Created: 20/Jan/22  Updated: 29/Oct/23  Resolved: 02/Feb/22

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 5.3.0

Type: Task Priority: Major - P3
Reporter: Haley Connelly Assignee: Daniel Gomez Ferro
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Sprint: Execution Team 2022-02-07
Participants:

 Description   

Investigate sharding_clustered_collections suite failure for collation_shard_targeting_hashed_shard_key.js

It hits the invariant that  disallows a collator from being specified for a clustered index scan



 Comments   
Comment by Githook User [ 02/Feb/22 ]

Author:

{'name': 'Daniel Gómez Ferro', 'email': 'daniel.gomezferro@mongodb.com', 'username': 'dgomezferro'}

Message: SERVER-62811 Allow special index types on cluster keys
Branch: master
https://github.com/mongodb/mongo/commit/c7f5e389e4488fcf7bd7a9a2ca4149080c409242

Comment by Daniel Gomez Ferro [ 21/Jan/22 ]

I think the problem is that we are creating a clustered collection with a collation and sharding it on _id. Since sharding requires an index on the shard key with the simple collation and it's currently not possible to create indexes on _id, it shouldn't be possible to end up in this state. Could it be due to the way we are forcing all collections to be clustered (using a failpoint I guess)?

Generated at Thu Feb 08 05:56:07 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.