[SERVER-79991] [CQF] Fallback to classic if we have a hashed shard key Created: 14/Aug/23  Updated: 29/Oct/23  Resolved: 15/Aug/23

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 7.1.0-rc0

Type: Bug Priority: Major - P3
Reporter: Ben Shteinfeld Assignee: Ben Shteinfeld
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Backwards Compatibility: Fully Compatible
Operating System: ALL
Participants:
Linked BF Score: 145

 Description   

After SERVER-78253, it is possible to have a hashed shard key without a backing index. As we haven't done SERVER-79853 yet, we need to explicitly fallback to classic if we encounter a hashed shard key.



 Comments   
Comment by Githook User [ 15/Aug/23 ]

Author:

{'name': 'Ben Shteinfeld', 'email': 'ben.shteinfeld@mongodb.com', 'username': 'bshteinfeld'}

Message: SERVER-79991 Fallback to classic when we encounter a collection with a
hashed shard key.

SERVER-78253 changed the behavior of dropIndexes() to drop hashed
indexes which are backing hashed shard keys. The fallback mechanism was
assuming that a hashed shard key will always have a backing hashed
index; now this assumption is no longer valid. This change explicitly
falls back when encountering a hashed shard key to account for cases
where the backing index is dropped.
Branch: master
https://github.com/mongodb/mongo/commit/e081fbfffed44b1db793ec412264d89be91223e1

Generated at Thu Feb 08 06:42:26 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.