[SERVER-42073] Server does not require hint() for min()/max() when IDHACK is used Created: 03/Jul/19  Updated: 27/Oct/23  Resolved: 22/Jul/19

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

Type: Bug Priority: Major - P3
Reporter: Ian Boros Assignee: Mikhail Ivkov (Inactive)
Resolution: Gone away Votes: 0
Labels: query-44-grooming
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
is related to SERVER-12916 Equality queries on _id don't obey mi... Closed
Sprint: Query 2019-07-29
Participants:

 Description   

In SERVER-39567 we changed min()/max() to require a hint(), but kay.kim discovered that this is not enforced when IDHACK is used.

I don't think there's an incorrect results bug here (similar to the linked ticket) but this is undesirable.

Repro:

db.c.find({_id: 5}).max({_id: 1}).explain()



 Comments   
Comment by Mikhail Ivkov (Inactive) [ 22/Jul/19 ]

Fixed as part of SERVER-12916.

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