[SERVER-46272] Make callers of keyBelongsToMe() to not go through collection metadata Created: 20/Feb/20  Updated: 27/Mar/20  Resolved: 25/Mar/20

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

Type: Task Priority: Major - P3
Reporter: Tommaso Tocci Assignee: Tommaso Tocci
Resolution: Duplicate Votes: 0
Labels: PM-1645-Milestone-1
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-45779 Throw Stale Shard Version when collec... Closed
is depended on by SERVER-32198 Missing collection metadata on the sh... Closed
Issue split
split to SERVER-47103 Add OrphanCleanupPolicy parameter to ... Closed
split to SERVER-47104 Make upsert stage use OwnershipFilter... Closed
split to SERVER-47105 Make update stage use OwnershipFilter... Closed
Sprint: Sharding 2020-03-23, Sharding 2020-04-06
Participants:

 Description   

keyBelongsToMe() functionality should now be accessed only through the new ScopedCollectionFilter class.

Thus it needs to be removed from the CollectionMetadata interface.

Probably we need also to migrate some of the CollectionMetadata unittest that make use of this functionality, such as src/mongo/db/s/collection_metadata_test.cpp



 Comments   
Comment by Tommaso Tocci [ 04/Mar/20 ]

In order to commit this we need getOwnershipFilter to throw an exception on StaleShardVersion when the collection is unknown

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