[SERVER-72678] [CQF] Rename CollationNode to avoid confusion with unicode collation comparison Created: 10/Jan/23 Updated: 19/Jan/23 |
|
| Status: | Open |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Nicholas Zolnierz | Assignee: | Backlog - Query Optimization |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Query Optimization
|
| Participants: |
| Description |
|
This node captures an ordering property for a value stream, which can be either sort or clustered. Using the term "collation" attempts to encapsulate both options but is now conflated with our unicode string comparison library. |
| Comments |
| Comment by Svilen Mihaylov (Inactive) [ 19/Jan/23 ] |
|
I believe that preserving the parallel between the collation property and the property enforcer is valuable and makes a lot of sense from the optimizers point of view. The collation requirement is a demand over the set of partial query result and the collation node is a way to satisfy the requirement. |