-
Notifications
You must be signed in to change notification settings - Fork 5.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Optimizer can not generate mpp plan when the index on generated column is visible #47766
Comments
/assign @AilinKid |
since the table schema is unclear, my possible guess is that: once the index path is visible, on our first optimizing rule:
Then, it will use this virtual column map, and try to substitute all the usage place down from tree root node, obviously the agg's arg has been substituted with the generated column to leverage the index if possible, but for latter check of tiflash path, we found that the agg's arg is a generate column is tiflash property enumeration is abandoned. |
and we see
and we see in the query select list, there is a item
so it is clear as I said before, In the original query with Note that, when this generated column substitution is finished, the |
Just show other plan enumeration with
this plan can be generated to leverage the most capability of tiflash, rather than use index in tikv, since |
Bug Report
Please answer these questions before submitting your issue. Thanks!
1. Minimal reproduce step (Required)
2. What did you expect to see? (Required)
mpp plan
3. What did you see instead (Required)
the table trades is access by index rather than by TiFlash mpp plan.
4. What is your TiDB version? (Required)
v7.1.1
The text was updated successfully, but these errors were encountered: