cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gary Dusbabek (JIRA)" <>
Subject [jira] Updated: (CASSANDRA-1038) Not all column families are created
Date Mon, 03 May 2010 22:22:56 GMT


Gary Dusbabek updated CASSANDRA-1038:

    Attachment: 0001-restrict-how-and-when-CFMetaData-objects-are-added-t.patch

The problem was that when the keyspace creation was reattempted, identical CFMetaData objects
were created that obliterated the older, correct cfids.

I could have put a check in the private CFMetaData constructor that threw an exception, but
decided I'd rather have explicit control over cfIdMap instead.

> Not all column families are created
> -----------------------------------
>                 Key: CASSANDRA-1038
>                 URL:
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 0.7
>            Reporter: Brandon Williams
>            Assignee: Gary Dusbabek
>             Fix For: 0.7
>         Attachments: 0001-restrict-how-and-when-CFMetaData-objects-are-added-t.patch
> It seems that not all column families will be created via system_add_keyspace in some
cases.  To reproduce:
> Run (with CASSANDRA-1033) inserts (I used 1M) against standard columns.  During
this run, both Standard1 and Super1 will be created.
> Run again, this time against super columns.  Due to CASSANDRA-1036 no errors
will be visible to the client but can be observed in the log.
> You can switch the order and stress supers first, in which case Standard1 will not exist.
 If you call describe_keyspace on Keyspace1, it will show both CFs even though only one will

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message