[SERVER-73010] Move ScanOrder into the metadata/PhysicalScanNode Created: 18/Jan/23  Updated: 15/Nov/23  Resolved: 15/Nov/23

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

Type: Improvement Priority: Major - P3
Reporter: Hana Pearlman Assignee: Militsa Sotirova
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-82876 [CQF] Add direction to PhysicalScanNo... Closed
Related
Assigned Teams:
Query Optimization
Backwards Compatibility: Fully Compatible
Sprint: QO 2023-11-13, QO 2023-11-27
Participants:

 Description   

SERVER-69895 will introduce ScanOrder on the SBENodeLowering object to support hinting a collection scan. Eventually, to support plans with multiple collection scans, we should move the ScanOrder to the scan definitions in the metadata and the PhysicalScanNodes.



 Comments   
Comment by Githook User [ 15/Nov/23 ]

Author:

{'name': 'Militsa Sotirova', 'email': 'militsa.sotirova@mongodb.com', 'username': 'militsasotirova'}

Message: SERVER-73010 Add ScanOrder to Metadata and PhysicalScanNode
Branch: master
https://github.com/mongodb/mongo/commit/4ad3698b2f071fc740ba5ed65da9bf3c76ed72f5

Comment by Militsa Sotirova [ 20/Oct/23 ]

Moving this into the correctness project since this information is a required part of the M2 explain output

Generated at Thu Feb 08 06:23:24 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.