You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@phoenix.apache.org by "Haitao Yao (JIRA)" <ji...@apache.org> on 2014/02/11 15:04:20 UTC

[jira] [Comment Edited] (PHOENIX-6) Support on duplicate key ignore construct

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

Haitao Yao edited comment on PHOENIX-6 at 2/11/14 2:04 PM:
-----------------------------------------------------------

[~jamestaylor]
Shall we add on duplicate key update syntax , too?
like this:
upsert into test_table values (xxxx) on duplicate key update time_stamp=XXX, other_attr=other_value;



was (Author: haitao.yao):
[~giacomotaylor]
Shall we add on duplicate key update syntax , too?
like this:
upsert into test_table values (xxxx) on duplicate key update time_stamp=XXX, other_attr=other_value;


> Support on duplicate key ignore construct
> -----------------------------------------
>
>                 Key: PHOENIX-6
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-6
>             Project: Phoenix
>          Issue Type: New Feature
>            Reporter: James Taylor
>            Assignee: Haitao Yao
>
> To support inserting a new row only if it doesn't already exist, we should support the "on duplicate key ignore" construct (or it's SQL standard equivalent) for UPSERT.
> See this discussion for more detail: https://groups.google.com/d/msg/phoenix-hbase-user/Bof-TLrbTGg/68bnc8ZcWe0J



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)