cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (JIRA)" <>
Subject [jira] [Updated] (CASSANDRA-4416) Include metadata for system keyspace itself in schema_* tables
Date Sat, 29 Sep 2012 19:04:07 GMT


Jonathan Ellis updated CASSANDRA-4416:

    Attachment: 4416.txt

Patch attached implementing Sylvain's suggestion to delete out and write anew the schema entries
for hardcoded tables.

Also removes SSTableExport restriction that you can only run it if non-system tables have
been defined which is kind of nonsensical.
> Include metadata for system keyspace itself in schema_* tables
> --------------------------------------------------------------
>                 Key: CASSANDRA-4416
>                 URL:
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>    Affects Versions: 1.2.0 beta 1
>            Reporter: paul cannon
>            Priority: Minor
>              Labels: cql, cql3
>             Fix For: 1.2.0 beta 2
>         Attachments: 4416.txt
> 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

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:

View raw message