Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-79851

[CQF] Store collation-op along with the shard key in optimizer metadata

    • Type: Icon: Task Task
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 7.1.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Fully Compatible
    • QO 2023-08-21
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      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.

            Assignee:
            ben.shteinfeld@mongodb.com Ben Shteinfeld
            Reporter:
            ben.shteinfeld@mongodb.com Ben Shteinfeld
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: