[SERVER-79851] [CQF] Store collation-op along with the shard key in optimizer metadata Created: 08/Aug/23 Updated: 29/Oct/23 Resolved: 16/Aug/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 7.1.0-rc0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Ben Shteinfeld | Assignee: | Ben Shteinfeld |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Sprint: | QO 2023-08-21 | ||||||||
| Participants: | |||||||||
| Description |
|
Currently we represent the shard key using the DistributionAndPaths struct. This struct is really about modeling the distribution/management of data between threads; it only stores the shard key as a vector of ABT paths, which is insufficient to model hashed shard keys. The goal of this ticket is to add the ability to represent hashed shard keys in the metadata and refactor the existing rewrites to reference this new representation. |
| Comments |
| Comment by Githook User [ 15/Aug/23 ] |
|
Author: {'name': 'Ben Shteinfeld', 'email': 'ben.shteinfeld@mongodb.com', 'username': 'bshteinfeld'}Message: This patch changes the optimizer's representation of the shard key from This patch also moves the shard key from DistributionAndPaths to |