[jira] Issue Comment Edited: (CASSANDRA-1704) CQL reads (aka SELECT)

["Jonathan Ellis (JIRA)" <ji...@apache.org>]

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

Jonathan Ellis edited comment on CASSANDRA-1704 at 11/4/10 5:15 PM:
--------------------------------------------------------------------

bq. what does `MARSHAL AS' do here?

It tells it how to turn column names into byte[]:
{code}SELECT 12345678-1234-5678-1234-567812345678 MARSHAL AS TimeUuid FROM timeline WHERE key = ...{code}

bq. As far as get_count() and multiget_count go

+1.  Although this points out that we should probably not overload COUNT as column limit too.  Maybe revise <COLUMNS> to

{code}<CDL>|(REVERSED? FIRST <N> <SLICE>) [MARSHAL AS <TYPE>]{code}

(here I have used parens as a grouping notation, not literals.  not sure how to disambiguate that.)

      was (Author: jbellis):
    bq. what does `MARSHAL AS' do here?

It tells it how to turn column names into byte[]:
{code}SELECT 12345678-1234-5678-1234-567812345678 MARSHAL AS TimeUuid FROM timeline WHERE key = ...{code}

bq. As far as get_count() and multiget_count go

+1.  Although this points out that we should probably not overload COUNT as column limit too.  Maybe revise <COLUMNS> to

{code}<CDL>|(REVERSED? FIRST <N> <SLICE>) [MARSHAL AS <TYPE>]{code}
  
> CQL reads (aka SELECT)
> ----------------------
>
>                 Key: CASSANDRA-1704
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-1704
>             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
>
> Data access specification and implementation for CQL.  
> This corresponds to the following RPC methods:
> * get()
> * get_slice()
> * get_count()
> * multiget_slice()
> * multiget_count()
> * get_range_slices()
> * get_indexed_slices()
> The initial check-in to trunk/ uses a syntax that looks like:
> {code:SQL}
> SELECT (FROM)? <CF> [USING CONSISTENCY.<LVL>] WHERE <EXPRESSION> [ROWLIMIT X] [COLLIMIT Y] [ASC|DESC]
> {code}
> Where:
> * <CF> is the column family name.
> * <EXPRESSION> consists of relations chained by the AND keyword.
> * <LVL> corresponds to one of the enum values in the RPC interface(s).
> What is still undone:
> * Support for indexes
> * Counts
> * 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.