[DOCS-5392] Document change to keysExamined for the IXSCAN stage in the 3.2 release notes Created: 07/May/15  Updated: 30/Oct/23  Resolved: 27/Jan/16

Status: Closed
Project: Documentation
Component/s: Server
Affects Version/s: None
Fix Version/s: Server_Docs_20231030

Type: Task Priority: Major - P3
Reporter: David Storch Assignee: Ravind Kumar (Inactive)
Resolution: Done Votes: 0
Labels: docs-3.2
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Documented
documents SERVER-16381 Index scans don't include the final "... Closed
Participants:
Days since reply: 8 years, 3 weeks ago

 Description   

In 2.4 and 2.6, nscanned was calculated as every matching key returned by the index scan plus any out-of-range key which was examined before seeking to the start of the next range. The same holds in 3.0 for the keysExamined statistic. However, this code always had a strange exception in which it did not count the last out-of-range key examined.

In the release notes we should document that, as of 3.2, the final out-of-range key (i.e. the "end" key) is counted towards keysExamined.

See SERVER-16381 for details.



 Comments   
Comment by Githook User [ 27/Jan/16 ]

Author:

{u'username': u'rkumar-mongo', u'name': u'ravind', u'email': u'ravind.kumar@10gen.com'}

Message: DOCS-5392 : nscanned/keysExamined "end" check update

R2: CR + addtl. feedback

R3: Further Refinement

Signed-off-by: kay <kay.kim@10gen.com>
Branch: master
https://github.com/mongodb/docs/commit/ee16a143c0b0aa3acd0689fa207a9ccf1a0ad13b

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