cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eric Evans (JIRA)" <>
Subject [jira] Commented: (CASSANDRA-1705) CQL writes (aka UPDATE)
Date Mon, 08 Nov 2010 17:33:09 GMT


Eric Evans commented on CASSANDRA-1705:

I'm not sure it was obvious from my last comment, but the attached patch to the CQL doc (and
the HTML copy) were meant to be a summation of the syntax/semantics discussed. If no one responds
then I'll assume we have consensus and that work can start to make the implementation match
(not responding is fine, as long as that __is__ what it means :)).

> CQL writes (aka UPDATE)
> -----------------------
>                 Key: CASSANDRA-1705
>                 URL:
>             Project: Cassandra
>          Issue Type: Sub-task
>          Components: API
>    Affects Versions: 0.8
>            Reporter: Eric Evans
>            Priority: Minor
>             Fix For: 0.8
>         Attachments: CQL.html, v1-0001-CASSANDRA-1705.-doc-update-for-proposed-UPDATE.txt
>   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}
<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.

View raw message