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

Refactor renamedPaths() helpers to support renames in either direction

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 4.3.1
    • Component/s: Aggregation Framework
    • Labels:
      None
    • Backwards Compatibility:
      Fully Compatible
    • Sprint:
      Query 2019-07-01

      Description

      During development of SERVER-5477 we realized that we have many of the utilities necessary to track whether the shard key is preserved throughout the pipeline up until the first $group, but these helpers we developed to work backwards through a pipeline (for use in $merge optimizations).

      We should add a library that can compute the new names of fields in either direction. It should be able to answer both:

      • Given the paths which represent the shard key before this stage, where are the values that represent the shard key after this stage's transformation takes effect?
      • Given the paths which represent the shard key after this stage, where are the values that represent the shard key before this stage's transformation takes effect?

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              george.wangensteen George Wangensteen
              Reporter:
              charlie.swanson Charlie Swanson
              Participants:
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: