[jira] [Commented] (CASSANDRA-4416) Include metadata for system keyspace itself in schema_* tables

["paul cannon (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/CASSANDRA-4416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13464419#comment-13464419 ] 

paul cannon commented on CASSANDRA-4416:
----------------------------------------

This is more important now, after CASSANDRA-4377, since as far as I can tell there is no way at all for a client or user to be able to see all the tables in the system and system_traces keyspaces.
                
> Include metadata for system keyspace itself in schema_* tables
> --------------------------------------------------------------
>
>                 Key: CASSANDRA-4416
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-4416
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>    Affects Versions: 1.2.0 beta 1
>            Reporter: paul cannon
>            Priority: Minor
>              Labels: cql, cql3
>
> The `system.schema_keyspaces`, `system.schema_columnfamilies`, and `system.schema_columns` virtual tables allow clients to query schema and layout information through CQL. This will be invaluable when users start to make more use of the CQL-only protocol (CASSANDRA-2478), since there will be no other way to determine certain information about available columnfamilies, keyspaces, or show metadata about them.
> However, the system keyspace itself, and all the columnfamilies in it, are not represented in the schema_* tables:
> {noformat}
> cqlsh> select * from system.schema_keyspaces where "keyspace" = 'system';
> cqlsh> 
> cqlsh> select * from system.schema_columnfamilies where "keyspace" = 'system';
> cqlsh> 
> cqlsh> select * from system.schema_columns where "keyspace" = 'system';
> cqlsh> 
> {noformat}
> It would be greatly helpful to clients which do more introspection than the minimum (say, for example, cqlsh) to be able to get information on the structure and availability of schema-definition tables.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira