[CASSANDRA-7566] DROP TABLE should also drop prepared statements associated to

• Type: Bug
• Status: Resolved
• Priority: Normal
• Resolution: Fixed
• Fix Version/s: 2.1.1
• Labels: bootcamp cql3

Environment

OSX 10.9.4 / JDK 1.8.0_05

• Severity: Normal
• Assignee: Viju Kothuvatiparambil Assign to me
• Reporter: Ben Hood

Authors

Viju Kothuvatiparambil

Reviewers

Tom Hobbs

• Created: 17/Jul/14 16:12
• Updated: 16/Apr/19 09:31
• Resolved: 17/Sep/14 01:24

Description

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.

Issue Links

• is duplicated by: CASSANDRA-8153 PreparedStatements broken when column family is recreated
• is related to: CASSANDRA-7910 wildcard prepared statements are incorrect after a column is added to the table