Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-84725 Create a single query settings module interface exposed to the system
  3. SERVER-87040

Create dedicated lookupQuerySettingsFor<Command> methods in query settings module

XMLWordPrintableJSON

    • Type: Icon: Sub-task Sub-task
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 8.0.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • Query Execution
    • Fully Compatible
    • QE 2024-03-18, QE 2024-04-01, QE 2024-04-15, QE 2024-12-09, QE 2024-12-23, QE 2025-01-06, QE 2025-01-20, QE 2025-02-03, QE 2025-02-17, QE 2025-03-03
    • None
    • 0
    • None
    • None
    • None
    • None
    • None
    • None

      Currently query settings are looked up via a query_settings::lookupQuerySettings() free function, which takes QueryShapeHash function as an argument.

      Since the number of commands supported by query settings is relatively small, we can avoid passing lambdas and instead have 3 separate methods for each command.

      Potentially we could move command specific logic there, if needed

            Assignee:
            denis.grebennicov@mongodb.com Denis Grebennicov
            Reporter:
            denis.grebennicov@mongodb.com Denis Grebennicov
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: