[
https://issues.apache.org/jira/browse/CASSANDRA-1704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12929184#action_12929184
]
Eric Evans commented on CASSANDRA-1704:
---------------------------------------
Attached is a patch that updates doc/cql/CQL.textile for the changes to SELECT
discussed in this issue so far (as I understand them). I'm not 100% on whether
to include all of >, >=, <, and <= for range specification considering that
these are always term inclusive. I'm also not sure 10,000 is the optimal
default limit for columns and keys (I used that as more or less a
place-holder). Both of these are minor nits and could be dealt with now or at
some point down-the-road, YMMV.
As a convenience, I also attached an HTML copy of the patched document,
(https://issues.apache.org/jira/secure/attachment/12459000/CQL.html).
> 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
>
> Attachments: CQL.html,
> v1-0001-CASSANDRA-1704.-doc-update-for-proposed-SELECT.txt
>
> 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.
