[
https://issues.apache.org/jira/browse/CASSANDRA-3140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13115893#comment-13115893
]
Jonathan Ellis commented on CASSANDRA-3140:
-------------------------------------------
bq. Can we leverage this approach to deliver "describe" functionality for
Keyspaces and Column Families?
That's what I proposed on CASSANDRA-3002. (It's more complicated though when
you're dealing w/ dynamic information.)
bq. Where would v$version be recognized as a special value and not a
non-existent CF?
As in the example above, I'm just using a *real* CF here, System.Versions. So
the issue doesn't arise.
bq. Can you use one of the known column names rather than "*"?
Yes, the patch adds a key alias of "component" (which my cli example doesn't
demonstrate, but I don't have cqlsh working yet via apache extras) and column
metadata for "version".
> Expose server, api versions to CQL
> ----------------------------------
>
> Key: CASSANDRA-3140
> URL: https://issues.apache.org/jira/browse/CASSANDRA-3140
> Project: Cassandra
> Issue Type: New Feature
> Reporter: Jonathan Ellis
> Assignee: Jonathan Ellis
> Priority: Minor
> Labels: cql
> Fix For: 1.0.1
>
> Attachments: 3140-patch.diff, 3140-patch1.diff, 3140-v3.txt
>
>
> Need to expose the CQL api version; might as well include the server version
> while we're at it.
--
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
