Refactor cluster_aggregate to use one collation

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Gone away
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Querying
    • Query 2020-09-07
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      In a code review, Charlie pointed out that in dispatchShardPipeline() we sometimes pass the collation from the request AggregationRequest when doing shard targeting, rather than passing the collation which is the default for the collection (which is computed here).

      We looked into it some more and could not find any incorrect behavior, but it might be worth doing a more thorough check, and refactor the code so that we only use one collation.

            Assignee:
            Nikita Lapkov (Inactive)
            Reporter:
            Ian Boros
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: