Consider propagating the version context to alternative client/opCtx

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Catalog and Routing
    • 🟩 Routing and Topology
    • None
    • None
    • None
    • None
    • None
    • None

      Consider the possibility to programmatically enforce passing a boost::optional<VersionContext> when spawning an alternative client or operation context e.g. when calling cc().makeOperationContext(). This way callers will always be "invited" to think about the possible implications of missing the version context potentially present on the parent client/opCtx.

            Assignee:
            Unassigned
            Reporter:
            Pierlauro Sciarelli
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated: