[SERVER-54848] listIndexes command lost ability to filter Created: 01/Mar/21  Updated: 06/Dec/22  Resolved: 09/May/22

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

Type: Bug Priority: Major - P3
Reporter: Mathias Stearn Assignee: Backlog - Storage Execution Team
Resolution: Won't Do Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Assigned Teams:
Storage Execution
Operating System: ALL
Participants:

 Description   

This may have happened as part of SERVER-52545 which IDLified the command with strict: true. The listIndexes command used to take all extra arguments and treat them as a filter for the indexes to return. You can see it in the js wrapper function. While it is a questionable API design, I'm not sure if we intended to break it. At the very least we should fix the JS wrapper to either not take a filter, or use the agg form and pass in a $match stage.



 Comments   
Comment by Connie Chen [ 09/May/22 ]

Since this affects the legacy shell we are closing this as "won't do"

Comment by Max Hirschhorn [ 01/Mar/21 ]

I don't believe the listIndexes command ever applied those extra arguments as a filter - see SERVER-18518.

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