Add willBeMerged flag to MongoExtensionCatalogContext

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Fixed
    • Priority: Major - P3
    • 9.0.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Query Integration
    • Fully Compatible
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Extensions currently use !inRouter as a proxy for requesting intermediate (unmerged) metadata from mongot. This breaks on single-shard/unsharded collections where inRouter=false but no merge follows, leaking unmerged metadata into output.

      Correct condition is !inRouter && needsMerge. Rather than exposing raw needsMerge (deprecated via SERVER-107416, lossy setter, overloaded), we compute it host-side and add a derived willBeMerged flag to MongoExtensionCatalogContext.

            Assignee:
            Aditya Deshpande
            Reporter:
            Aditya Deshpande
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: