[jira] Commented: (CASSANDRA-1705) CQL writes (aka UPDATE)

["Jim Ancona (JIRA)" <ji...@apache.org>]

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

Jim Ancona commented on CASSANDRA-1705:
---------------------------------------

Any reason not to make it more SQL-like, e.g.
{noformat}
UPDATE <CF> 
SET KEY=<key>, <cname1> = <cvalue1>, <cname2> = <cvalue2>,  ...
{noformat}
The column names would allow the same kinds of literals and type specs as the values, as opposed to SQL where they're just identifiers.

You could do multi-row updates (which SQL doesn't allow) by delimiting them with the 'KEY =' clause, like:
{noformat}
UPDATE <CF> 
SET KEY=<key>, <cname11> = <cvalue11>, <cname12> = <cvalue12>,  ...
        KEY=<key2>, <cname21> = <cvalue21>, <cname22> = <cvalue22>,  ...
{noformat}

> 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.