-
Notifications
You must be signed in to change notification settings - Fork 613
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
fix & refactor(table): use dist_key_in_pk
instead of distribution_key
#8377
Comments
c.c. @yuhao-su @BugenZhao @wcy-fdu |
LGTM |
Off the topic, it seems the concept of |
currently, the distribution key seems an internal concept. Users can not specify the distribution key for any table/mview or internal table and they are all generated by the optimizer. Users can use create index to influence the final distribution key, but it is just physical implementation behind the logical concept such as |
Although it is an internal concept, the user performance might be affected by dist key when it's cardinality is extremely low (e.g. the dist key is gender) Users may want to know the cause? |
I thought the doc maintained on Github intends to be developer-facing 🤔 |
oh, sorry, I get it now. |
dist_key_in_pk
instead of distribution_key
dist_key_in_pk
instead of distribution_key
In our system, all the table's distribution keys are always in the primary key. And we are more care about the distribution key from the primary key or its prefix for partition pruning.
https://github.com/singularity-data/risingwave/blob/main/src/stream/src/common/table/state_table.rs
https://github.com/singularity-data/risingwave/blob/main/src/storage/src/table/batch_table/storage_table.rs
Also, the distribution keys can not express the actual indices in the read prefix, especially when the primary key has duplications. #7698
dist_key_in_pk
field in the table's proto. use it to fix panicked atvnode 151 should not be accessed by this table
#7698dist_key_in_pk
and remove thedistribution_key
fieldThe text was updated successfully, but these errors were encountered: