Test the defaulting of uniqueKey when the catalog cache is stale

XMLWordPrintableJSON

    • Fully Compatible
    • Query 2018-09-10, Query 2018-09-24, Query 2018-10-08, Query 2018-10-22, Query 2018-11-05
    • 45
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      We added some testing of what happens when an $out is executing with a stale cache, but we'd like to target the functionality introduced in SERVER-35954 which will also read the cache.

      This will include the interesting test case of seeing what unique key is used if a mongos has a stale version of the cache which indicates that a collection is sharded but it actually is not, or if it is sharded but now with a different key.

              Assignee:
              Charlie Swanson
              Reporter:
              Charlie Swanson
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: