pingcap/tidb

Call For Participation: SIG-Planner 2020/Q1 Plan

Open

#14,609 opened on Feb 3, 2020

View on GitHub
 (0 comments) (7 reactions) (0 assignees)Go (40,090 stars) (6,186 forks)batch import
help wantedsig/planner

Description

We list the the 2020 Q1's development plan of the planner. If you're interested in some of the features. You can just join the **sig-planner` channel in the TiDB's community slack workspace to have detailed talk with us. Each issue has its own sub issues. You can open the one you're interested to get more information. Some of the issues are in early stage, any discusstions is welcome. We're waiting for you!

O1: Improve the existing features of the planner

  • KR: Make SQL Plan Mangement production ready.
  • KR: Make prepare plan cache more stable.
  • KR: Make statistics more stable.
  • KR: Add some stability test for join reorder
  • KR: Make the new SQL Hint production ready
    • Finish Join Order Hint
    • Add tests for SQL Hint
    • Finish NO_PRED_PUSH hint. Part of #14608

O2: Enlarge the search spaces of the planner

  • KR: Develop the new cascades planner. #13709
  • KR: Maintaining the NULL information #14616
  • KR: Support the suquery in JOIN’s ON clause. #11414
  • KR: Let join reorder support OUTER JOIN #9268
  • KR: Let PointGet be a physical choice of the TiKV DataSource. #14044

O3: Improve the planner’s usability

  • KR: Recording the index usage information and more #14607
  • KR: Develop the Optimizer Trace. #14143
  • KR: Refine EXPLAIN’s output #14603
  • KR: Implement the index advisor. #12303
  • KR: Supplyment Reference Manual document

Contributor guide

Tech stack
gosql
Domain
database
Issue type
chore
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
5
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
over 1 week
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
unclear
Prerequisites
Query optimization conceptsTiDB architectureGo programmingDatabase internals
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
10
Research direction
This is a meta issue listing development objectives. To contribute, review the sub issues referenced (e.g., #13709, #14616) and join the sig planner Slack channel for details. The issue does not provide a specific deliverable; instead, identify a sub issue with clear scope and ask maintainers for guidance.