[SERVER-59660] Allow change stream rewrites for $match with non-simple collation Created: 28/Aug/21 Updated: 06/Dec/22 Resolved: 03/Oct/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Justin Seyster | Assignee: | Backlog - Query Execution |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||
| Assigned Teams: |
Query Execution
|
||||||||||||||||||||
| Participants: | |||||||||||||||||||||
| Description |
|
SERVER-59659 would eliminate the need for that restriction, but even if that does not turn out to be practical, some rewrites can still be applied in pipelines with non-simple collations. Fields such as clusterTime, which cannot have a string value, can be rewritten normally. Rewrites for fields that can have arbitrary strings would need to go in a separate $match, which does not get pushed down to the $cursor level of the pipeline. |
| Comments |
| Comment by Bernard Gorman [ 03/Oct/21 ] |
|
Closing this as a duplicate of SERVER-59659. The two requests are not exactly the same, but SERVER-59659 proposes a more expansive solution and can be used to consider both alternatives. |