[SERVER-53637] Allow collation to be specified for a $lookup sub-pipeline Created: 07/Jan/21  Updated: 29/Oct/23  Resolved: 14/May/21

Status: Closed
Project: Core Server
Component/s: Aggregation Framework
Affects Version/s: None
Fix Version/s: 5.0.0-rc0

Type: New Feature Priority: Major - P3
Reporter: Charlie Swanson Assignee: James Wahlin
Resolution: Fixed Votes: 0
Labels: query-work-resharding
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
is depended on by SERVER-53940 Support resuming resharding collectio... Backlog
Related
related to SERVER-65080 Support the SBE pushdown of $lookup w... Backlog
is related to SERVER-25954 Support more granular collation speci... Backlog
Backwards Compatibility: Fully Compatible
Sprint: Query Execution 2021-03-08, Query Optimization 2021-03-22, Query Optimization 2021-04-05, Query Optimization 2021-04-19, Query Optimization 2021-05-03, Query Optimization 2021-05-17
Participants:

 Description   

As part of the resharding effort we need to run a pipeline with the collection's default collation, but then use the simple collation for a specific comparison concerning the chunk boundaries.

This ticket tracks the work to add that ability. Note this is different and narrower than SERVER-25954, since we need this relatively soon and it is believed that SERVER-25954 is a pretty substantial engineering effort. 



 Comments   
Comment by Githook User [ 14/May/21 ]

Author:

{'name': 'James Wahlin', 'email': 'james@mongodb.com', 'username': 'jameswahlin'}

Message: SERVER-53637 Add internal $lookup sub-pipeline collation
Branch: master
https://github.com/mongodb/mongo/commit/2bc171077dfa0186fb38324bb720be254067559f

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