cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sylvain Lebresne (JIRA)" <>
Subject [jira] [Updated] (CASSANDRA-4416) Include metadata for system keyspace itself in schema_* tables
Date Wed, 03 Oct 2012 07:02:08 GMT


Sylvain Lebresne updated CASSANDRA-4416:

    Attachment: 4416_fix.txt

The problem being, when we load the table from the system table, the system ones have already
been loaded and shouldn't be loaded a second time. Attaching a patch that ignore the system
keyspaces when reading schema tables (we only write those for client sake, we never need them
internally, so let just do as if they weren't there).
> 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
>            Assignee: Jonathan Ellis
>            Priority: Minor
>              Labels: cql, cql3
>             Fix For: 1.2.0 beta 2
>         Attachments: 4416_fix.txt, 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