[SERVER-42206] Make DocumentSourceSample use SortExecutor instead of DocumentSourceSort Created: 12/Jul/19  Updated: 06/Dec/22  Resolved: 27/Sep/19

Status: Closed
Project: Core Server
Component/s: Aggregation Framework, Querying
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Major - P3
Reporter: David Storch Assignee: Backlog - Query Team (Inactive)
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-41960 Factor SortExecutor out of DocumentSo... Closed
depends on SERVER-42176 Consolidate agg sort key generation c... Closed
Assigned Teams:
Query
Sprint: Query 2019-08-12, Query 2019-08-26
Participants:

 Comments   
Comment by David Storch [ 27/Sep/19 ]

After speaking with pawel.terlecki, we've decided to close this as Won't Fix. In the long term, we imagine that we will not have a special DocumentSourceSample stage, but will rather expand the unoptimized sample path into a PROJECT(randVal) => SORT(randVal) => LIMIT plan.

Comment by Kelly Lewis [ 27/Aug/19 ]

david.storch since Mikhail is no longer with MongoDB, assigning this to the Query backlog FYI 

Generated at Thu Feb 08 04:59:52 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.