Loading...

XML

Word

Printable

JSON

Type: Task
Resolution: Fixed
Priority: Major - P3
Fix Version/s: 8.1.0-rc0, 8.0.0-rc4
Affects Version/s: None
Component/s: None
Labels:
None

Assigned Teams:

Query Integration
Backwards Compatibility:
Fully Compatible
Backport Requested:

v8.0
Sprint:
QI 2024-04-01, QI 2024-04-15, QI 2024-04-29, QI 2024-05-13
Linked BF Score:
33
CAR Domain/s:
None

Aha! Reference:
None
Tracking Level:
None
Risk Status:
None
Exec Notes:
None
Goal Name(s):
None
Goal Link:
None

Currently we only use DISTINCT_SCAN in a $group for last and first accumulators following a sort. Expand to also use DISTINCT_SCAN for top and bottom accumulators.

causes

SERVER-110803 $top and $bottom ignore sortBy clause when preceeding $sort stage makes it eligible for DISTINCT_SCAN optimization

Closed

is related to

SERVER-90017 Parse firstN/lastN/minN/maxN/topN/bottomN with n = 1 into a corresponding first/last/min/max/top/bottom

Closed

related to

SERVER-112844 Nested $elemMatch query can uassert when multiple predicates are present

Closed

SERVER-85213 Rewrite $sort+$group with $first/$last to use $top/$bottom

Backlog

SERVER-107953 DISTINCT_SCAN with $top and $bottom is only used when grouping field is included as sort prefix

Backlog

Assignee:: Yoon Soo Kim (Inactive)
Reporter:: Naama Bareket
Participants:: Githook User, Naama Bareket, Yoon Soo Kim
Votes:: 0 Vote for this issue
Watchers:: 5 Start watching this issue

Created:: Dec 20 2023 05:08:20 PM UTC
Updated:: Oct 24 2025 09:10:06 PM UTC
Resolved:: Apr 30 2024 03:26:14 AM UTC

Details

Description

Attachments

Issue Links

Activity

People

Dates