cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eric Evans (JIRA)" <j...@apache.org>
Subject [jira] Commented: (CASSANDRA-1705) CQL writes (aka UPDATE)
Date Sat, 06 Nov 2010 20:12:22 GMT

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

Eric Evans commented on CASSANDRA-1705:
---------------------------------------

> Incidentally, superficially it looks like SQL multi-row insert would be a good
> fit here; see http://en.wikipedia.org/wiki/Insert_%28SQL%29#Multirow_inserts.

Oh please no.

> The problem is that this syntax does too little to distinguish between row keys
> and column names; while this is okay for insert-as-insert it is baffling for
> insert-as-update.  UPDATE is also a better semantic fit since people are used to
> seeing that with a sparse list of column names.

Agreed.


> CQL writes (aka UPDATE)
> -----------------------
>
>                 Key: CASSANDRA-1705
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-1705
>             Project: Cassandra
>          Issue Type: Sub-task
>          Components: API
>    Affects Versions: 0.8
>            Reporter: Eric Evans
>            Priority: Minor
>             Fix For: 0.8
>
>   Original Estimate: 0h
>  Remaining Estimate: 0h
>
> CQL specification and implementation for data manipulation.
> This corresponds to the following RPC methods:
> * insert()
> * batch_mutate() (writes, not deletes)
> The initial check-in to trunk/ uses a syntax that looks like:
> {code:SQL}
> UPDATE <CF> [USING CONSISTENCY.<LVL>] WITH ROW(<key>, COLUMN(<name>,
<value>)[, COLUMN(...)])[ AND ROW(...)];
> {code}
> Where:
> * <CF> is the column family name.
> * Rows are a parenthesized expressions with comma separated arguments for a key and one
or more columns.
> * Columns are a parenthesized expressions with comma separated arguments for the name
and value (timestamp is inaccessible).
> What is still undone:
> * Complete test coverage
> And of course, all of this is still very much open to further discussion.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message