[ https://issues.apache.org/jira/browse/CASSANDRA-1704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12928987#action_12928987 ]
Jim Ancona commented on CASSANDRA-1704: --------------------------------------- > Under what circumstances would you even want to encode a result to a type > that was different than the one used to validate and/or sort it for storage? I was thinking mostly of cases where type information isn't available. Right now, there is no type information available for keys and validation_class is optional for column values. For that reason, I think the ability to specify it for key and column values is important. I agree that it's not necessary for column names, especially in a first release, since the comparator type is always available. > 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.