[SERVER-5016] last error incorrectly set when an in memory sort assertion occurs during a query but results returned correctly from another plan Created: 20/Feb/12  Updated: 15/Feb/13  Resolved: 24/Oct/12

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

Type: Bug Priority: Major - P3
Reporter: Aaron Staple Assignee: Unassigned
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
duplicates SERVER-4953 clean/fix exception handling in query... Closed
Operating System: ALL
Participants:

 Description   

A scanandorder memory assertion for one plan shouldn't propagate to the client via last error if another query plan sends query results normally.

Test will be pushed.



 Comments   
Comment by auto [ 25/Feb/12 ]

Author:

{u'login': u'astaple', u'name': u'Aaron', u'email': u'aaron@10gen.com'}

Message: SERVER-5016 be more careful about checking last error appropriately, was causing a problem in sharding passthgouh tests with different last error behavior
Branch: master
https://github.com/mongodb/mongo/commit/a7f7be16cdd8e95ba0f36a19824f75662b5ce184

Comment by auto [ 25/Feb/12 ]

Author:

{u'login': u'astaple', u'name': u'Aaron', u'email': u'aaron@10gen.com'}

Message: SERVER-4150 SERVER-5016 additional sort and explain checks in sortg test
Branch: master
https://github.com/mongodb/mongo/commit/43aa6577ae38c7183e50f0cadc96191d27d324db

Comment by auto [ 20/Feb/12 ]

Author:

{u'login': u'astaple', u'name': u'Aaron', u'email': u'aaron@10gen.com'}

Message: SERVER-5016 test
Branch: master
https://github.com/mongodb/mongo/commit/e5f47c8131661893039a032ee25806f2a5307776

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