[SERVER-45384] Add support for unordered object comparison in MQL Created: 06/Jan/20  Updated: 06/Dec/22

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

Type: New Feature Priority: Major - P3
Reporter: Mihai Andrei Assignee: Backlog - Query Execution
Resolution: Unresolved Votes: 0
Labels: qexec-team
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Assigned Teams:
Query Execution
Participants:

 Description   

Currently, there is no simple way to perform an unordered object comparison in MQL. It would be helpful to have an expression like $unorderedEq that would allow this.



 Comments   
Comment by David Storch [ 24/Jan/20 ]

jack.mulrow, I'll move it to the query team's backlog. This is a useful general enhancement to the language outside of the context of finding inconsistent indexes on the shards.

Comment by Jack Mulrow [ 22/Jan/20 ]

david.storch, charlie.swanson, it turns out we didn't need to implement this (we used Asya's trick to sort each object's fields with $objectToArray, $setUnion, and $arrayToObject instead) - do you want me to move this to the query backlog, or should I close it?

Comment by Jack Mulrow [ 09/Jan/20 ]

david.storch I agree it would make sense for sharding to do this ticket, since we need it for a sharding project. We're hoping to avoid doing this work at all by changing how we detect inconsistent indexes to use JavaScript instead of an aggregation, but in case it does end up being necessary I took your suggestion and moved it into the indexes epic / assigned it to the sharding backlog.

Comment by David Storch [ 09/Jan/20 ]

mihai.andrei jack.mulrow which team is going to do the work for this? I was under the assumption that the sharding team would do the work, and the query team will review. If this is the case, then I think this ticket should be added to the epic and moved to the sharding backlog.

Comment by Charlie Swanson [ 07/Jan/20 ]

mihai.andrei and david.storch our understanding is that this ticket is required for the project to ensure indexes are consistent on all shards? Should it be linked to something? Based on that assumption, we've slotted it into the next sprint and gave it the fixVersion "4.3 Required". Let me know if that's reasonable.

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