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

Michael Shuler reopened CASSANDRA-7566:
---------------------------------------

The merge of this patch to trunk causes a build failure on trunk.  Seems to 
build OK for me on the cassandra-2.1 branch.
http://cassci.datastax.com/job/trunk/1069/console
{noformat}
    [javac] 
/home/mshuler/git/cassandra/src/java/org/apache/cassandra/cql3/QueryProcessor.java:515:
 error: MigrationSubscriber is not abstract and does not override abstract 
method onDropFunction(String,String) in IMigrationListener
    [javac]     private static class MigrationSubscriber implements 
IMigrationListener
    [javac]                    ^
{noformat}

> DROP TABLE should also drop prepared statements associated to
> -------------------------------------------------------------
>
>                 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: Viju Kothuvatiparambil
>              Labels: bootcamp, cql3
>             Fix For: 2.1.1
>
>         Attachments: trunk-7566.txt
>
>
> 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.3.4#6332)

Reply via email to