[SERVER-15403] $min and $max equal errors in 2.6 but not in 2.4 Created: 25/Sep/14  Updated: 11/Jul/16  Resolved: 01/Oct/14

Status: Closed
Project: Core Server
Component/s: Querying
Affects Version/s: 2.6.4, 2.7.6
Fix Version/s: 2.6.6, 2.7.8

Type: Bug Priority: Minor - P4
Reporter: Andrew Emil (Inactive) Assignee: David Storch
Resolution: Done Votes: 0
Labels: 28qa
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
Operating System: ALL
Backport Completed:
Steps To Reproduce:

var t = db.sameminmax;
t.drop();
 
t.ensureIndex({a:1});
assert.throws(function() {t.find().min({a:1}).max({a:1}).toArray()});

Sprint: Query 2.7.8
Participants:

 Description   

Using the same value for min and max will throw an error in 2.6 while in 2.4 it would succeed but never return any documents.



 Comments   
Comment by Githook User [ 18/Nov/14 ]

Author:

{u'username': u'dstorch', u'name': u'David Storch', u'email': u'david.storch@10gen.com'}

Message: SERVER-15403 query planner should not error if $min and $max are equal

(cherry picked from commit 88e79e1b476996bab2582009f4ab5ff7c9fad9f4)
Branch: v2.6
https://github.com/mongodb/mongo/commit/cdcda1cd39528c6f2c732ccb7972f7726596c834

Comment by Githook User [ 01/Oct/14 ]

Author:

{u'username': u'dstorch', u'name': u'David Storch', u'email': u'david.storch@10gen.com'}

Message: SERVER-15403 query planner should not error if $min and $max are equal
Branch: master
https://github.com/mongodb/mongo/commit/88e79e1b476996bab2582009f4ab5ff7c9fad9f4

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