cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brandon Williams (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-7566) DROP/CREATE TABLE cycle causes unrecognized column family
Date Thu, 17 Jul 2014 16:37:06 GMT

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

Brandon Williams commented on CASSANDRA-7566:
---------------------------------------------

bq. CASSANDRA-5202 appears to have been fixed in 2.1 beta1, but the version I'm using is 2.1-rc3.
Is 2.1 beta 1 a newer release than 2.1-rc3?

No; my mistake.  Sorry.

> DROP/CREATE TABLE cycle causes unrecognized column family
> ---------------------------------------------------------
>
>                 Key: CASSANDRA-7566
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-7566
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>         Environment: OSX 10.9.4 / JDK 1.8.0_05
>            Reporter: Ben Hood
>            Assignee: Yuki Morishita
>
> An integration test suite that drops and creates the same column family 3 times causes
the following error in the server log:
> INFO  15:40:34 Initializing gocql_test.wiki_page
> ERROR 15:40:34 Attempted to write commit log entry for unrecognized column family: b0e167e0-0dc8-11e4-9cbb-29a4872887f2
> ERROR 15:40:34 Attempting to mutate non-existant column family b0e167e0-0dc8-11e4-9cbb-29a4872887f2
> ERROR 15:40:34 Attempted to write commit log entry for unrecognized column family: b0e167e0-0dc8-11e4-9cbb-29a4872887f2
> ERROR 15:40:34 Attempting to mutate non-existant column family b0e167e0-0dc8-11e4-9cbb-29a4872887f2
> The test that reproduces this issue is here:
> https://github.com/gocql/gocql/blob/master/wiki_test.go
> Interestingly this issue only occurs after the common table is dropped/created for the
3rd time. If only one of the tests is run on its own, this issue does not arise.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message