Skip to content
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

sql: support partitioned hash sharded index #13087

Closed
cockroach-teamcity opened this issue Feb 22, 2022 · 1 comment
Closed

sql: support partitioned hash sharded index #13087

cockroach-teamcity opened this issue Feb 22, 2022 · 1 comment

Comments

@cockroach-teamcity
Copy link
Member

cockroach-teamcity commented Feb 22, 2022

Exalate commented:

cockroachdb/cockroach#76358 --- Release note (sql change): Previously, crdb blocked users from creating hash sharded index in all kinds of partitioned tables including implict partitioned tables using PARTITION ALL BY or REGIONAL BY ROW. Now we turn on the support of hash sharded index in implicit partitioned tables. Which means primary key cannot be hash sharded if a table is explicitly partitioned with PARTITION BY or an index cannot be hash sharded if the index is explicitly partitioned with PARTITION BY. Paritioning columns cannot be placed explicitly as key columns of a hash sharded index as well, including regional-by-row table's crdb_region column.

Jira Issue: DOC-2711

@exalate-issue-sync
Copy link

Nick Vigilante (nickvigilante) commented:
[https://cockroachlabs.slack.com/archives/CARM0PTK4/p1644268878041489|https://cockroachlabs.slack.com/archives/CARM0PTK4/p1644268878041489|smart-card]

An implicitly partitioned table is a table that is partitioned with {{PARTITION ALL BY}} or {{REGIONAL BY ROW}}. An explicitly partitioned table is partitioned with {{PARTITION BY}}.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants