[SERVER-46372] Use unordered object comparison in aggregation for finding inconsistent sharded indexes Created: 24/Feb/20  Updated: 27/Oct/23  Resolved: 13/Mar/20

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

Type: Bug Priority: Major - P3
Reporter: Jack Mulrow Assignee: [DO NOT USE] Backlog - Sharding Team
Resolution: Gone away Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-29425 Add an expression to sort an array Closed
Assigned Teams:
Sharding
Operating System: ALL
Participants:

 Description   

The aggregation used to find sharded indexes that aren't on all shards with chunks (added by SERVER-44916 and modified by SERVER-46084) only considers a subset of the possible properties in an index specification when comparing them to work around the inability to cleanly compare BSON objects ignoring field order in aggregation. After SERVER-29425 adds official support for ordering an array, the pipeline should be updated to compare entire index specifications with unordered object comparisons using $objToArray, the new sort expression, and then $arrayToObj.



 Comments   
Comment by Jack Mulrow [ 13/Mar/20 ]

As part of SERVER-46084 a way to perform unordered BSON object comparison was found that doesn't require a sorting expression, so closing this ticket as Gone Away.

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