Migrate scatterGatherVersionedTargetByRoutingTable functions to take in RoutingContext instead of CRI

XMLWordPrintableJSON

    • Query Integration
    • Fully Compatible
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      This is the first step of enforcing the contract that a RoutingContext used for a routing operation can only be safely destructed if it has its routing tables validated by sending a versioned request to a shard.

      The following functions will be migrated over to the RoutingContext:

      • scatterGatherVersionedTargetByRoutingTable
      • scatterGatherVersionedTargetByRoutingTableNoThrowOnStaleShardVersionErrors

      Any code that calls into these functions must acquire their routing tables through. the RoutingContext instead of directly accessing the CatalogCache.

              Assignee:
              Lynne Wang
              Reporter:
              Lynne Wang
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: