[ https://issues.apache.org/jira/browse/CASSANDRA-7566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14065136#comment-14065136 ]
Yuki Morishita commented on CASSANDRA-7566: ------------------------------------------- [~0x6e6562], does gocql use prepared statement? I'm guessing we need to drop prepared statement too when dropping columnfamily. > 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)