[SERVER-38901] Resolve and remove code reference to closed SERVER-18346 Created: 08/Jan/19  Updated: 06/Dec/22

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

Type: Task Priority: Major - P3
Reporter: Dianna Hohensee (Inactive) Assignee: Backlog - Query Execution
Resolution: Unresolved Votes: 0
Labels: qexec-team
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-18346 Investigate interaction of Collection... Closed
Assigned Teams:
Query Execution
Sprint: Execution Team 2019-08-12, Execution Team 2019-11-04, Execution Team 2019-12-02
Participants:
Linked BF Score: 0

 Description   

Explore how the code works and determine whether CollectionInfoCacheImpl::updatePlanCacheIndexEntries needs to include unfinished indexes in the query plan cache updates. If not, the plan cache probably needs to be updated at the end of the index build rather than the beginning.



 Comments   
Comment by Eric Milkie [ 09/Dec/19 ]

From a conversation with Ian, it seems like the only thing that still gets populated when we update the "PlanCacheIndexEntries" is a Discriminator map, and that map is only used to generate a plan cache key for a query, prior to planning. It's unclear whether we can stop putting unfinished indexes in this. If we can, we just need to move the call to "addedIndex()" to be after the catalog is updated with a newly built index as "ready:true" – today, it is called when the catalog is in the state with "ready:false".

Comment by Eric Milkie [ 31/Jul/19 ]

Note that the IndexUsageTracker is involved here, so if we changed this to not include unfinished indexes, it could result in stats changes in the IndexUsageTracker.

Generated at Thu Feb 08 04:50:23 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.