[
https://issues.apache.org/jira/browse/CASSANDRA-2474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13185249#comment-13185249
]
Jonathan Ellis commented on CASSANDRA-2474:
-------------------------------------------
bq. The '..' notation for slices is removed
Personally I'd rather support both for one release to make the transition
easier, but with neither super nor composite support I doubt many people are
using the current .., so if doing both adds a lot of complexity I'm okay with
this.
bq. I've made static definitions (i.e, those definitions that don't use COMPACT
STORAGE basically) really static.
I'm a little uneasy about this, but the only use cases I've been able to come
up with make more sense as a COMPACT STORAGE wide row. So it's probably a good
change.
bq. Currently, prepared statement allows you to write SELECT ? FROM users WHERE
? > 3. I.e, you can have marker in place of a column definition (I call 'column
definition' a name defined in the CREATE TABLE basically). I think it could
make sense to disallow that.
+1
bq. However, when you do say SELECT * FROM CF; (of if you query multiple keys
with IN), then it's unclear what you do with the LIMIT
I don't think it's unclear at all, but maybe that's because of my SQL
background. :) Granted, it doesn't make a great deal of sense to use IN +
LIMIT, but if someone does, the LIMIT should take precedence.
bq. I'm also not sure have the REVERSED just after the SELECT is still the
right choice after this patch.
What if we allowed "ORDER BY DESC" instead? (This is not quite valid SQL,
which requires "ORDER BY <expr> [ASC|DESC]", but it's close.)
> CQL support for compound columns and wide rows
> ----------------------------------------------
>
> Key: CASSANDRA-2474
> URL: https://issues.apache.org/jira/browse/CASSANDRA-2474
> Project: Cassandra
> Issue Type: New Feature
> Components: API, Core
> Reporter: Eric Evans
> Assignee: Sylvain Lebresne
> Priority: Critical
> Labels: cql
> Fix For: 1.1
>
> Attachments: 2474-transposed-1.PNG, 2474-transposed-raw.PNG,
> 2474-transposed-select-no-sparse.PNG, 2474-transposed-select.PNG,
> cql_tests.py, raw_composite.txt, screenshot-1.jpg, screenshot-2.jpg
>
>
> For the most part, this boils down to supporting the specification of
> compound column names (the CQL syntax is colon-delimted terms), and then
> teaching the decoders (drivers) to create structures from the results.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
