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

CanonicalQuery should own a CollatorInterface

    XMLWordPrintableJSON

Details

    • Task
    • Status: Closed
    • Major - P3
    • Resolution: Done
    • None
    • 3.3.8
    • Querying
    • None
    • Fully Compatible
    • Query 13 (04/22/16), Query 14 (05/13/16)

    Description

      • The query_planner library needs to depend on collator_factory_interface.
      • CanonicalQuery::canonicalize() should take an additional OperationContext* parameter.
      • Add a unique_ptr<CollatorInterface> to member to CanonicalQuery, initialized using CollatorFactoryInterface decorated on the service context.

      Attachments

        Issue Links

          depends on

          Task - A task that needs to be done. SERVER-23348 Add a collator to ComparisonMatchExpression, InMatchExpression

          • Major - P3 - Major loss of function.
          • Closed

          Improvement - An improvement or enhancement to an existing feature or task. SERVER-24045 Refactor LiteParsedQuery and CanonicalQuery::canonicalize()

          • Major - P3 - Major loss of function.
          • Closed
          is depended on by

          Task - A task that needs to be done. SERVER-23611 Query planner should set collation from collection default if query lacks user-specified collation

          • Major - P3 - Major loss of function.
          • Closed

          Task - A task that needs to be done. SERVER-23613 StageBuilder::build() should propagate collator from CanonicalQuery to relevant PlanStages

          • Major - P3 - Major loss of function.
          • Closed

          Activity

            People

              tess.avitabile@mongodb.com Tess Avitabile (Inactive)
              rassi J Rassi
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: