[
https://issues.apache.org/jira/browse/CASSANDRA-4161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13257361#comment-13257361
]
Christoph Tavan commented on CASSANDRA-4161:
--------------------------------------------
I'm wondering why CQL is being parsed in the client at all? Couldn't we just
handle the exceptions thrown by cassandra? That way we wouldn't have to keep
cqlsh in sync with CQL development on the C*-side.
> CQL 3.0 does not work in cqlsh with uppercase SELECT
> ----------------------------------------------------
>
> Key: CASSANDRA-4161
> URL: https://issues.apache.org/jira/browse/CASSANDRA-4161
> Project: Cassandra
> Issue Type: Bug
> Components: Tools
> Affects Versions: 1.1.0
> Environment: cqlsh
> Reporter: Jonas Dohse
> Priority: Minor
> Labels: cql3, cqlsh
> Attachments:
> 0001-Allow-CQL-3.0-with-uppercase-SELECT-statement.patch, 4161.patch.txt
>
>
> Uppercase SELECT prevents usage of CQL 3.0 features like ORDER BY
> Example:
> select * from test ORDER BY number; # works
> SELECT * from test ORDER BY number; # fails
--
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
