-
Type: Task
-
Resolution: Fixed
-
Affects Version/s: None
-
Component/s: None
-
None
-
Fully Compatible
-
Query Optimization 2021-06-14
Its possible that we could share partition key comparision code with the PartitionIterator to optimize memory usage in the non-full cases. Since we're sorting by
{partitionFields, densifyField}we can throw away data from previous partitions once we've seen a value from the next partition.
- is depended on by
-
SERVER-57339 Add support for partitionByFields in parsing and desugaring
- Closed
-
SERVER-57340 Add support for partitioning in DocumentSourceDensify for range: full
- Closed
-
SERVER-57342 Add support for explicit ranges with partitions
- Closed
-
SERVER-57344 Add support for partitioning and range: partition
- Closed