Aggregations on sharded view with concurrent drops and create can ignore view definitions

XMLWordPrintableJSON

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

      Repro steps:

      1. Run any query on a sharded view (view A backed by collection B).
      2. After the 'CommandOnShardedViewNotSupportedOnMongod' is raised and while mongos is resolving the view, we drop collection B and recreate it as view B on collection C.
      3. We will finish the query but not apply the view pipeline from view A and only apply view B's definition.

      Found and related to the viewless timeseries upgrade/downgrade effort (see SERVER-120567), but it is not specific to viewless timeseries.

            Assignee:
            Gil Alon
            Reporter:
            Gil Alon
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: