[SERVER-18019] Consolidate "index filter applied" query planning stats logic for explain/planCacheListCommands Created: 13/Apr/15  Updated: 06/Dec/22  Resolved: 02/Aug/19

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

Type: Bug Priority: Major - P3
Reporter: J Rassi Assignee: Backlog - Query Team (Inactive)
Resolution: Won't Do Votes: 0
Labels: query-44-grooming
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Assigned Teams:
Query
Operating System: ALL
Participants:

 Description   

The "plans.filterSet" field from the planCacheListPlans command output is generated by piping a boolean to the cache through the following member variables:

  • QueryPlannerParams::indexFiltersApplied
  • QuerySolution::indexFilterApplied
  • SolutionCacheData::indexFilterApplied

In contrast, the "queryPlanner.indexFilterSet" field for the explain command is supported by directly accessing the QuerySettings for the given collection (which may be out of date).

These approaches should be unified and simplified.



 Comments   
Comment by David Storch [ 02/Aug/19 ]

Closing as "Won't Do". The planCacheListPlans command has been marked as deprecated for the 4.2 release, so we do not plan to schedule work to improve its implementation.

Generated at Thu Feb 08 03:46:18 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.