explain.queryPlanner.winningPlan.stage A string that denotes the name of the stage. Each stage consists of information specific to the stage. For example, anIXSCANstage includes the index bounds along with other data specific to the index scan. If a stage has a child stage or multiple child...
/* planner will not cope with utility statements */ if (query->commandType == CMD_UTILITY) { ExplainOneUtility(query->utilityStmt, into, es, queryString, params, queryEnv); return; } /* if an advisor plugin is present, let it manage things */ if (ExplainOneQuery_hook) (*ExplainOneQu...
You can see that although there’s an index on thediscarded_atcolumn, the query planner instead decided to use aSeq ScanwithFilteroperation. It’s not a mistake, and your index is not broken. It means that in case a query is expected to return a high portion of an underlying table in...
A string that specifies thenamespacewith the names of the database and the collection accessed by the query. The namespace has the format<database>.<collection>. explain.queryPlanner.indexFilterSet A boolean that specifies whether MongoDB applied anindex filterfor the计划缓存查询结构. ...
explain.queryPlanner.winningPlan.stage A string that denotes the name of the stage. Each stage consists of information specific to the stage. For example, an IXSCAN stage includes the index bounds along with other data specific to the index scan. If a stage has a child stage or multiple ...
explain.queryPlanner.winningPlan.stage A string that denotes the name of the stage. Each stage consists of information specific to the stage. For example, anIXSCANstage includes the index bounds along with other data specific to the index scan. If a stage has a child stage or multiple child...
explain.queryPlanner.winningPlan.stage A string that denotes the name of the stage. Each stage consists of information specific to the stage. For example, anIXSCANstage includes the index bounds along with other data specific to the index scan. If a stage has a child stage or multiple child...