-
Type:
Task
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: None
-
Query Integration
-
Fully Compatible
-
None
-
3
-
TBD
-
None
-
None
-
None
-
None
-
None
-
None
-
None
See Design Doc for the 4 scenarios we care about.
This should fail nicely due to unrecognized agg stage when the extensions are not loaded.
We should definitely test the expected behavior for standalone and sharded cluster. Maybe also 1-shard cluster? Maybe also a unsharded collections with a query that only targets 1 shard which does have the extension enabled – is it expected that that would succeed even if the cluster has nodes without extension enabled?
- related to
-
SERVER-109450 Investigate flaky createView() behavior during upgrade/downgrade
-
- Backlog
-
-
SERVER-109457 Test more replset upgrade/restart scenarios
-
- Backlog
-
-
SERVER-109554 Clarify ShardingTest.shardColl API
-
- Backlog
-