-
Type:
New Feature
-
Resolution: Done
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: None
-
Query Execution
-
Fully Compatible
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Create a server parameter that provides more fine-grained control than notablescan. Limit collection scans and full index scans to some constant. At planning time we can use the collection size to estimate this limit. In the presence of multi-key indexes we would not get a strict limit, but that's OK for the first implementation.
Note that this kind of reverts some of what was done in SPM-1024. However, the goal here is something more intelligent than maxScan and different than maxTimeMS – we want to reject queries before starting their execution (like notablescan).
Any attempt to do this should start by reviewing the findings of WRITING-33020.
- is depended on by
-
TOOLS-4259 Investigate changes in SERVER-127688: Reject queries that will perform a full COLLSCAN on a large collection
-
- Closed
-
- is related to
-
SERVER-130345 Add JS integration test for PQS $natural hint override of maxEstimatedScanBytes
-
- Closed
-
- related to
-
SERVER-130688 maxEstimatedScanBytes rejected/rejectedAndOverridden/dryRunWouldReject metrics overcounted for rooted $or queries
-
- Closed
-
-
SERVER-130345 Add JS integration test for PQS $natural hint override of maxEstimatedScanBytes
-
- Closed
-
-
SERVER-130968 Evaluate OTel metrics for maxEstimatedScanBytes rejection counters
-
- Investigating
-