[COMPASS-7253] compound index usage count not increasing on usage Created: 24/Sep/23  Updated: 25/Sep/23

Status: Open
Project: Compass
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Rajesh singh Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

OS: Windows and Mac



 Description   

Problem Statement/Rationale

What is going wrong? What action would you like the Engineering team to take?

Please be sure to attach relevant logs with any sensitive data redacted.
How to retrieve logs for: Compass; Shell

Steps to Reproduce

How could an engineer replicate the issue you’re reporting?

Expected Results

What do you expect to happen?

Actual Results

What do you observe is happening?

Additional Notes

Any additional information that may be useful to include.



 Comments   
Comment by Rhys Howell [ 25/Sep/23 ]

Hi singh.rs7777@gmail.com Thanks for opening the issue. Can you give us more information to help us understand what's going on:

  • What other indexes do you have on the collection? If you're using two fields which have other indexes on those fields it's likely those indexes are taking precedence over the compound index.
  • What query are you running that you expect the index usage to occur after?
  • What does the data look like: the field names and types?
Comment by Rajesh singh [ 24/Sep/23 ]

On Windows and macOS MongoDB compass, even after repeated usage of compound indexes, usage of compound indexes always show zero.

Comment by PM Bot [ 24/Sep/23 ]

Hello singh.rs7777@gmail.com, thank you for reaching out to us! The team will review your issue and get back to you soon as soon as possible.

Please review your issue to ensure you've included your environment details and have attached relevant logs (with any sensitive data redacted), so that we're best able to provide you a timely and thorough response. Thanks again!

Generated at Wed Feb 07 22:45:56 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.