-
Notifications
You must be signed in to change notification settings - Fork 3.8k
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: prohibit PARTITION [ALL] BY for multiregion tables #59719
Labels
A-multiregion
Related to multi-region
C-enhancement
Solution expected to add code/behavior + preserve backward-compat (pg compat issues are exception)
Comments
otan
added
C-enhancement
Solution expected to add code/behavior + preserve backward-compat (pg compat issues are exception)
A-multiregion
Related to multi-region
labels
Feb 2, 2021
otan
changed the title
sql: decide whether we allow PARTITION [ALL] BY for non-REGIONAL BY ROW tables
sql: decide whether we allow PARTITION [ALL] BY for multiregion tables
Feb 3, 2021
otan
added a commit
to otan-cockroach/cockroach
that referenced
this issue
Mar 4, 2021
Release justification: non-production code change Release note: None
Is this issue also meant to block moving to multi-region tables if there are zone configs present (at the database or table level)? If not, is there another issue for that? |
yeah this is the blanket issue |
otan
changed the title
sql: decide whether we allow PARTITION [ALL] BY for multiregion tables
sql: prohibit PARTITION [ALL] BY for multiregion tables
Mar 4, 2021
craig bot
pushed a commit
that referenced
this issue
Mar 5, 2021
61515: sql: prevent tables with PARTITION BY clauses from becoming multi-region r=ajstorm a=otan Release justification: low-risk update to new functionality Release note: None Refs #59719 61523: geo/geomfn: implement ST_Snap r=otan a=alsohas This patch implements ST_Snap. Resolves #49040 Release justification: low risk, high benefit changes to existing functionality Release note (sql change): ST_Snap is now available. 61528: roachtest: bump activerecord adapter tests to 6.1.0beta2 r=rafiss a=otan Release justification: non-production code change Release note: None Co-authored-by: Oliver Tan <otan@cockroachlabs.com> Co-authored-by: Abdullah Islam <abdullah_islam@uri.edu>
otan
added a commit
to otan-cockroach/cockroach
that referenced
this issue
Mar 5, 2021
Release justification: non-production code change Release note: None
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
A-multiregion
Related to multi-region
C-enhancement
Solution expected to add code/behavior + preserve backward-compat (pg compat issues are exception)
A lot of code at the moment assumes vanilla PARTITION BY statements. If the user defines their own PARTITION BY on these tables, what should we do? Block them? Allow them but promise nothing when altering between locality configs?
The text was updated successfully, but these errors were encountered: