[
https://issues.apache.org/jira/browse/CASSANDRA-3700?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13181420#comment-13181420
]
Sylvain Lebresne commented on CASSANDRA-3700:
---------------------------------------------
Is there a real advantage to allow the use of key alias *or* KEY. That is, why
don't we just allow the key alias, and have this be KEY (which we already do)
by default for CF created through thrift without a proper key_alias (case that
is hopefully bound to disappear). The fact that we reserve KEY (and key too I
believe) is kind of limiting in that you cannot use KEY for some other column.
Besides, the KEY notation will be slightly less meaningful post-2474 because it
will not necessarily correspond to the primary key anymore (i.e, it may
correspond only to the first column column that compose the PRIMARY KEY).
> SelectStatement start/end key are not set correctly when a key alias is
> involved
> --------------------------------------------------------------------------------
>
> Key: CASSANDRA-3700
> URL: https://issues.apache.org/jira/browse/CASSANDRA-3700
> Project: Cassandra
> Issue Type: Bug
> Components: API
> Affects Versions: 0.8.1
> Reporter: Jonathan Ellis
> Assignee: Pavel Yaskevich
> Labels: cql
> Fix For: 1.0.8
>
> Attachments: CASSANDRA-3700.patch
>
>
> start/end key are set by antlr in WhereClause, but this depends on the "KEY"
> keyword.
--
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
