[
https://issues.apache.org/jira/browse/CASSANDRA-3010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13082402#comment-13082402
]
Jonathan Ellis commented on CASSANDRA-3010:
-------------------------------------------
bq. Is this syntax going to be available to clients of CQL queries at run time,
or is this just a CLI grammar addition?
The latter. (Which matches every other language + db shell combination I have
seen.)
bq. I believe the functionality of the "describe" needs to be available at
runtime.
Agreed, but not by adding extra syntax to CQL itself (CASSANDRA-2477).
bq. By "cli", do you mean "cqlsh"? If not, how will a CQL shell avoid breaking
scripts that use the cli's syntax?
That was my way of saying "we should make a new tool, and leave the existing
cli alone for backwards compatibility."
> Java CQL command-line shell
> ---------------------------
>
> Key: CASSANDRA-3010
> URL: https://issues.apache.org/jira/browse/CASSANDRA-3010
> Project: Cassandra
> Issue Type: New Feature
> Components: Tools
> Reporter: Jonathan Ellis
> Assignee: Pavel Yaskevich
> Fix For: 1.0
>
>
> We need a "real" CQL shell that:
> - does not require installing additional environments
> - includes "show keyspaces" and other introspection tools
> - does not break existing cli scripts
> I.e., it needs to be java, but it should be a new tool instead of replacing
> the existing cli.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
