phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "James Taylor (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (PHOENIX-940) Unique Constraint
Date Fri, 02 May 2014 05:22:14 GMT

    [ https://issues.apache.org/jira/browse/PHOENIX-940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13987345#comment-13987345
] 

James Taylor commented on PHOENIX-940:
--------------------------------------

So you'd like to be able to add to the PK for a VIEW, right? The reason is that you don't
want the row with the same entity_id to be updated again and again, but you'd rather maintain
all of those versions as independent/separate rows.

Is that correct, [~elilevine]?

> Unique Constraint
> -----------------
>
>                 Key: PHOENIX-940
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-940
>             Project: Phoenix
>          Issue Type: New Feature
>            Reporter: Eli Levine
>
> Add support for UNIQUE constraint on one or more columns in CREATE and ALTER TABLE statements:
> {code}
> CONSTRAINT constraint_name UNIQUE (column1, column2, . column_n)
> {code}
> One possible way to implement this is by adding a secondary index on columns involved
in the constraint and adding a check for column values before upsert.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message