-
Type: Task
-
Resolution: Unresolved
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
Query Integration
For time-series multi updates, the spool stage could use memory exceeding the limit and would need to spill to disk. By default, we allow queries and commands to spill to disk if necessary. But if users would like to fail early on their (potentially mistakenly wrong) non-selective updates, we want to provide them a more fine-control way to do so per command.
- related to
-
SERVER-74437 Implement spilling to disk in new classic SPOOL stage
- Closed