pingcap/tidb

Use a new struct to store the props generated by `preparePossibleProperties`

Open

#10,749 创建于 2019年6月10日

在 GitHub 查看
 (0 评论) (1 反应) (2 负责人)Go (40,090 star) (6,186 fork)batch import
help wantedsig/plannertype/performance

描述

after https://github.com/pingcap/tidb/pull/10548 There'll be multiple props which share the same suffix. We can implement a struct which can store the eqPrefixLen to cut off the possible props then reduce the search space.

贡献者指南

技术栈
go
领域
databaseperformance
议题类型
refactor
难度面向新贡献者的预计实现难度，1 表示很小改动，5 表示专家级工作。
4
预计时间有经验贡献者完成调查、实现、测试并准备 pull request 的粗略时间范围。
half day
活动状态议题当前的可参与程度：新鲜、活跃、陈旧、阻塞或等待维护者输入。
stale
清晰度议题是否清楚说明期望改动、验收标准和下一步。
mostly clear
前置要求
Go programmingTiDB internals
新手友好度1-100 的估计分数，表示该议题对首次贡献者的友好程度。
25
研究方向
Review the referenced PR #10548 to understand the background about multiple props sharing suffixes. Look at the current implementation of `preparePossibleProperties` in the TiDB source code to identify where the new struct should be introduced. The goal is to encapsulate `eqPrefixLen` and the props in a struct to reduce search space. There are no comments or additional guidance, so the contributor may need to propose a design in the issue first.