-
Type:
Improvement
-
Resolution: Won't Do
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
Query Integration
-
None
-
None
-
None
-
None
-
None
-
None
-
None
When a read against a non-materialized view is performed in a sharded cluster, the read is first sent to the primary shard for the database, which then looks up the view definition and returns to mongos as part of a CommandOnShardedViewNotSupportedOnMongod error response. We could consider instead performing the rewrite locally on the primary shard and then performing shard to shard routing. This would save us a network hop from the primary shard back to mongos.
- depends on
-
SERVER-123781 Mixed-binary / multiversion fixtures still enable IFR flags on “new” mongods (and mongos) when feature-flag suites are on
-
- Closed
-
- is related to
-
SERVER-121859 Aggregations on sharded view with concurrent drops and create can ignore view definitions
-
- Closed
-
-
SERVER-74826 Errors CommandOnShardedViewNotSupportedOnMongod on sharded view
-
- Closed
-
- related to
-
SERVER-65949 Sharded time series leads to high query rates on the primary shard with CommandOnShardedViewNotSupportedOnMongod errors
-
- Blocked
-
-
SERVER-121988 $lookup on sharded view with concurrent drops and create matches no documents
-
- In Progress
-
-
SERVER-124442 Add CommandHelpers::runWithCommandErrorHandling and use it in count_cmd
-
- Closed
-
-
SERVER-124443 Add explain_common::appendCleanedExplainResponseFromSubrouter helper
-
- Closed
-
-
SERVER-124444 Add pipeline_factory overload accepting an already-parsed LiteParsedPipeline
-
- Closed
-
-
SERVER-124445 Implement shard-side view resolution helper
-
- Closed
-
-
SERVER-124446 Introduce `isFromAggregateCommand` concept through aggregate commands
-
- Closed
-
-
SERVER-124462 Add a remote resolved namespaces cache to AggExState
-
- Closed
-
-
SERVER-49228 Remove kickback to mongos requirement for cluster view read when view is backed by unsharded collection
-
- Closed
-