[SERVER-62647] Rationalize behavior of RandomCursor for scan stage Created: 14/Jan/22  Updated: 06/Dec/22

Status: Backlog
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Major - P3
Reporter: Svilen Mihaylov (Inactive) Assignee: Backlog - Query Execution
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Assigned Teams:
Query Execution
Participants:

 Description   

Currently we use the scan stage's random cursor to achieve on-the-fly sampling estimation for the new optimizer.

 

The presence of a random cursor might not be ideal from an engineering point of view, and may become redundant in the near future as more advanced CE techniques are developed which will supersede the sampling.

This work is to track progress on the CE front, and possibly remove the random cursor in the future when it is no longer needed.



 Comments   
Comment by Rushan Chen [ 04/Oct/22 ]

svilen.mihaylov@mongodb.com we are going through the tickets. What is the exact ask here in terms of changes to deliver?

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