Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Message-ID: <26840407.437661285657773707.JavaMail.jira@thor>
Date: Tue, 28 Sep 2010 03:09:33 -0400 (EDT)
From: "Gary Dusbabek (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Subject: [jira] Updated: (CASSANDRA-1548) renaming a keyspace, then trying
 to use original name again makes errorations
In-Reply-To: <24965164.431251285627353789.JavaMail.jira@thor>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/CASSANDRA-1548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gary Dusbabek updated CASSANDRA-1548:
-------------------------------------

    Attachment: v1-0001-ensure-that-a-table-unloads-CFS-instances-when-they-ar.txt

> renaming a keyspace, then trying to use original name again makes errorations
> -----------------------------------------------------------------------------
>
>                 Key: CASSANDRA-1548
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-1548
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 0.7 beta 2
>         Environment: encountered on Debian squeeze, with cassandra from HEAD (r1001931).  effects can be seen with both Telephus and Pycassa as clients; probably any.
>            Reporter: paul cannon
>            Assignee: Gary Dusbabek
>            Priority: Minor
>             Fix For: 0.7.0
>
>         Attachments: test_case_1548.py, v1-0001-ensure-that-a-table-unloads-CFS-instances-when-they-ar.txt
>
>
> My test case does the following:
> * Create a keyspace with at least one CF in it.
> * Rename that keyspace
> * Create a new keyspace with the same original name, containing a CF with the same name as earlier.
> The second keyspace creation receives an error (although the keyspace does get created):
> {{javax.management.InstanceAlreadyExistsException: org.apache.cassandra.db:type=ColumnFamilies,keyspace=keyspacename,columnfamily=cfname}}
> After that point, trying to do almost anything with the new keyspace will generate the same error- even trying to drop it. This persists until cassandra itself is restarted.
> One supposes that some JMX thing is lacking reregistration upon keyspace rename.

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