[SERVER-63078] Show when clustered index is used in explain and slow query logs Created: 28/Jan/22  Updated: 29/Oct/23  Resolved: 04/Feb/22

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

Type: Improvement Priority: Major - P3
Reporter: Louis Williams Assignee: Louis Williams
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Documented
is documented by DOCS-15091 Investigate changes in SERVER-63078: ... Backlog
Backwards Compatibility: Minor Change
Sprint: Execution Team 2022-02-07
Participants:

 Description   

Slow queries on clustered collections report a COLLSCAN, but it's not clear that this is actually a bounded scan over a clustered collection..

Additionally, the explain output reports minRecord and maxRecord, but we should include a flag that specifically indicates that this was a ranged scan over a clustered collection,



 Comments   
Comment by Githook User [ 03/Feb/22 ]

Author:

{'name': 'Louis Williams', 'email': 'louis.williams@mongodb.com', 'username': 'louiswilliams'}

Message: SERVER-63078 Report bounded clustered collections scans as CLUSTERED_IXSCAN

Bounded scans on clustered collections will display a CLUSTERED_IXSCAN stage in
the slow query logs and explain output. Clustered collection scans without
bounds will continue to display a COLLSCAN.
Branch: master
https://github.com/mongodb/mongo/commit/04aea22a1bdffec3ff69a73bb85f089efad14b6f

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