[SERVER-31443] $changeStream pipelines should support non-simple collations Created: 06/Oct/17  Updated: 30/Oct/23  Resolved: 03/Nov/17

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

Type: Task Priority: Major - P3
Reporter: Tess Avitabile (Inactive) Assignee: Charlie Swanson
Resolution: Fixed Votes: 0
Labels: todo_in_code
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
is related to SERVER-31442 $changeStream pipelines should inheri... Closed
is related to SERVER-31447 Ensure change stream update lookup us... Closed
Backwards Compatibility: Fully Compatible
Sprint: Repl 2017-10-23, Repl 2017-11-13
Participants:

 Description   

Currently $changeStream pipelines error when the pipeline collation is non-simple. $changeStream pipelines should support non-simple collations. Comparisons within the $changeStream stage itself should use binary comparison (e.g. comparing namespace string, shard key, _id (comparing _id can also use the collection default collation)), but subsequent stages in the pipeline should use the pipeline collation as usual. This will allow users to do collation-aware comparisons in $match stages in a $changeStream pipeline, which is essential for users using collation.



 Comments   
Comment by Githook User [ 03/Nov/17 ]

Author:

{'name': 'Charlie Swanson', 'username': 'cswanson310', 'email': 'charlie.swanson@mongodb.com'}

Message: SERVER-31443 Add support for change streams with non-simple collations.
Branch: master
https://github.com/mongodb/mongo/commit/265fa69f73e083e07c0092d62dc0f5ed54bc9cfe

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