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

Refactor Sharded Aggregation code

    • Type: Icon: Improvement Improvement
    • Resolution: Unresolved
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Query Execution
    • QE 2024-09-16, QE 2024-09-30, QE 2024-10-14, QE 2024-10-28, QE 2024-11-11, QE 2024-11-25

      See linked tickets for some ideas, but generally, this ticket captures the work to refactor/improve the structure of the following files:

      This ticket is fairly open ended, but some ideas:

      • There are quite a few places where we have special cases for change streams, $documents, etc. Perhaps we should consider refactoring these special cases out (i.e.  SERVER-43874), or at least restructure the code in such a way that we don't have a bunch of special case checks scattered throughout the code.
      • Similarly, there seem to be separate cases for those aggregates which require a CollectionRoutingInfo and those that don't. We should consider splitting these, as doing so would enable us to acquire the CRI in exactly one spot (as opposed to throughout the sharded agg code path; i.e. SERVER-83658)

            Assignee:
            mickey.winters@mongodb.com Mickey Winters
            Reporter:
            mihai.andrei@mongodb.com Mihai Andrei
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated: