cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Viju Kothuvatiparambil (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CASSANDRA-7566) DROP TABLE should also drop prepared statements associated to
Date Sun, 14 Sep 2014 18:00:34 GMT

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

Viju Kothuvatiparambil updated CASSANDRA-7566:
----------------------------------------------
    Attachment: trunk-7566.txt

A patch to this issue is attached along with a test class. The QueryProcessor class now listens
to the changes to schema, and cleanups prepared statements on drop keyspace and drop table
events.  This is done by implementing IMigrationListener inside QueryProcessor and registering
the listener with MigrationManager. This patch can be enhanced to fix the related issues,
but this being my first contribution to Cassandra, I would like the experts to comment on
it before I work on the others.  (My sincere thanks to Tylor Hobbs, Aleksey Yeschenko and
Brandon Williams, Joshua McKenzie and Marcus Eriksson for helping me out at the cassandra
developer bootcamp)

> 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: Yuki Morishita
>              Labels: 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)

Mime
View raw message