cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Stupp (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-8335) Support CAS with UPDATE...IF col=val OR NOT EXISTS
Date Tue, 18 Nov 2014 21:19:35 GMT

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

Robert Stupp commented on CASSANDRA-8335:
-----------------------------------------

Given that particular use case, it might be better to do {{INSERT ... IF NOT EXISTS}} if current_value==null
and {{UPDATE ... IF ...}} if not.

But (although I do not recall a use case for UPDATE...OR NOT EXISTS) there might be some reason
for this. It does not seem unlikely that a result might have been computed to value X or never
computed.

Would like to keep this ticket unresolved until someone comes up with a real-world scenario
for this.

> Support CAS with UPDATE...IF col=val OR NOT EXISTS
> --------------------------------------------------
>
>                 Key: CASSANDRA-8335
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-8335
>             Project: Cassandra
>          Issue Type: New Feature
>          Components: Core
>            Reporter: Robert Stupp
>            Priority: Minor
>              Labels: cas, cql
>
> On the -dev mailing list the RFE to extend UPDATE LWT using something like
> {{UPDATE ... IF col=val ... OR NOT EXISTS}}
> RFE is to add the {{OR NOT EXISTS}} which means either the the {{IF}} conditions are
met *xor* the row does not exist.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message