Make CollectionCatalog API safer by removing getters exposing raw pointers

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Catalog and Routing
    • CAR Team 2025-11-24, CAR Team 2025-12-08
    • 3
    • 🟦 Shard Catalog
    • None
    • None
    • None
    • None
    • None
    • None

      Currently the catalog API exposes functions which return raw pointers and it is up to the caller to ensure they never use a pointer after a yield, as was in the case in SERVER-105873. This situation could become less likely if the API only returned smart pointers. Then this type of mistake would become less severe as it would not crash/UB.

            Assignee:
            Jordi Olivares Provencio
            Reporter:
            Ben Shteinfeld
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated: