[SERVER-57338] Investigate factoring out PartitionIterator partition comparison code Created: 01/Jun/21  Updated: 29/Oct/23  Resolved: 07/Jun/21

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 5.1.0-rc0

Type: Task
Reporter: Joe Kanaan Assignee: Ted Tuckman
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
is depended on by SERVER-57339 Add support for partitionByFields in ... Closed
is depended on by SERVER-57340 Add support for partitioning in Docum... Closed
is depended on by SERVER-57342 Add support for explicit ranges with ... Closed
is depended on by SERVER-57344 Add support for partitioning and rang... Closed
Backwards Compatibility: Fully Compatible
Sprint: Query Optimization 2021-06-14
Participants:

 Description   

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.



 Comments   
Comment by Vivian Ge (Inactive) [ 06/Oct/21 ]

Updating the fixversion since branching activities occurred yesterday. This ticket will be in rc0 when it’s been triggered. For more active release information, please keep an eye on #server-release. Thank you!

Comment by Githook User [ 07/Jun/21 ]

Author:

{'name': 'Ted Tuckman', 'email': 'ted.tuckman@mongodb.com', 'username': 'TedTuckman'}

Message: SERVER-57338 Separate partition checking code from PartitionIterator
Branch: master
https://github.com/mongodb/mongo/commit/754b77a3ddb2605402e333fbdfcacc371f899379

Generated at Thu Feb 08 05:41:35 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.