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

Allow users to create UNIQUE indexes on partition column for HASH and RANGE distributed tables. #130

Closed
sumedhpathak opened this issue Feb 3, 2016 · 5 comments
Assignees
Labels
Milestone

Comments

@sumedhpathak
Copy link
Contributor

Currently, we error out when users try to create UNIQUE indexes on distributed tables. However, we can allow users to create indexes on partition columns for HASH and RANGE distributed tables.

@ozgune
Copy link
Contributor

ozgune commented Feb 8, 2016

Item #222 talks about enforcing these constraints at table creation time. We'd like for the user experience to be similar for ALTER TABLE changes.

Also, this issue could be related to #192.

@onderkalaci
Copy link
Member

I think we should somehow unify the checks on create index and create table when considering the add this feature. Basically, there should be a single function which checks all these uniqeness constraints.

@sumedhpathak
Copy link
Contributor Author

@mtuncer Could you look into this issue after your current tasks? @onderkalaci should be able to give you context on the change.

@mtuncer
Copy link
Member

mtuncer commented Mar 14, 2016

@sumedhpathak are we sure about enabling unique on range partitioned tables ? AFAIK we could not enforce disjointness on the range tables since one can create shards with overlapping ranges.

@onderkalaci
Copy link
Member

@mtuncer But don't we have that assumption for all functionalities of range tables? Don't we expect the users to ensure that shards are non-overlapping for range partitioned tables?

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

No branches or pull requests

5 participants