[SERVER-24096] Consider making MultikeyPaths a class Created: 08/May/16  Updated: 06/Dec/22

Status: Backlog
Project: Core Server
Component/s: Internal Code, Querying
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Major - P3
Reporter: Max Hirschhorn Assignee: Backlog - Query Optimization
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Assigned Teams:
Query Optimization
Participants:

 Description   

Based on codereview feedback during SERVER-22726, having a class to represent the cross product of "the index is multikey" and "the index has path-level multikey information" would improve the readability of the code in plan_enumerator.cpp, index_catalog_entry.cpp, etc. It would be possible to then fold the currently separate code paths for when the index is multikey but doesn't have path-level info and when the index is multikey and has path-level info.

https://github.com/mongodb/mongo/blob/r3.3.5/src/mongo/db/index/multikey_paths.h#L37-L43


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