-
Type:
Bug
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: None
-
None
-
Query Integration
-
Fully Compatible
-
ALL
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Repro steps:
- Run any query on a sharded view (view A backed by collection B).
- 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.
- 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.
- is depended on by
-
SERVER-120567 Queries on views over a timeseries collection are racy with FCV upgrade/downgrade
-
- Closed
-
- related to
-
SERVER-121988 $lookup on sharded view with concurrent drops and create matches no documents
-
- Backlog
-
-
SERVER-42282 Consider replacing CommandOnShardedViewNotSupportedOnMongod mechanism with rewrite / routing from shard
-
- In Progress
-