MongoByte MongoDB Logo

Welcome to the new MongoDB Feedback Portal!

{Improvement: "Your idea"}
We’ve upgraded our system to better capture and act on your feedback.
Your feedback is meaningful and helps us build better products.

Add new feedback Subscribe
Status Will Not Implement
Categories Data Modeling & Indexing
Created by surovskyi.y@ajax.systems surovskyi.y@ajax.systems
Created on Nov 11, 2025

RELATED FEEDBACK

Provide safe canary deployment mechanism for index changes

What problem are you trying to solve?

Focus on the what and why of the need you have, not the how you'd like it solved.

1. Unreliable index usage data

2. All-or-nothing risk with hideIndex()

No ability to test on a subset of traffic or for a limited time period

What would you like to see happen?

Describe the desired outcome or enhancement.

How I see it
1st option
db.users.hideIndex("index_1", { duration: "5m", autoRollback: { slowQueryThreshold: 100 } });

2nd option
db.users.hideIndex("index_1", { duration: "5m", members: { tag: ""READONLY } });

Why is this important to you or your team?

Explain how the request adds value or solves a business need.

We've had incidents where hiding an index caused production issues that took 15+ minutes to detect and resolve

Fear of mistakes leads to conservative approach → accumulating technical debt

What steps, if any, are you taking today to manage this problem?



  • Admin
    Katya Kamenieva
    Nov 25, 2025

    Hello, thank you for your feedback. There are no plans to implement the proposed features for hiding indexes. I would recommend looking into Query Settings feature that can be used for more granular control of index usage (per query shape).

    Also, we would need more information on "Unreliable index usage data". I suggest filing a more specific feedback item, including details on which tool was used for insights into index usage and how it didn't work out.

    Reply