Remove primary parser from $vectorSearch

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 8.3.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • Query Integration
    • Fully Compatible
    • ALL
    • 200
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Currently we register both the primary and fallback parser for $vectorSearch. However, this doesn't make sense as the primary parser should be the $vectorSearch extension (if present) while the fallback should be the legacy parser.

      Registering both as the legacy parser serves no purpose and will fail upon any $vectorSearch extension being loaded due to there already being a primary parser.

            Assignee:
            Josh Siegel
            Reporter:
            Josh Siegel
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: