Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Tue, 20 Jan 2015 18:43:35 +0000 (UTC)
From: "Edward Ribeiro (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12768740.1421779254000.125988.1421779415613@Atlassian.JIRA>
In-Reply-To: <JIRA.12768740.1421779254000@Atlassian.JIRA>
References: <JIRA.12768740.1421779254000@Atlassian.JIRA>
 <JIRA.12768740.1421779254656@arcas>
Subject: [jira] [Updated] (CASSANDRA-8652) DROP TABLE should also drop BATCH
 prepared statements associated to
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Edward Ribeiro updated CASSANDRA-8652:
--------------------------------------
    Labels: cql3  (was: )

> DROP TABLE should also drop BATCH prepared statements associated to
> -------------------------------------------------------------------
>
>                 Key: CASSANDRA-8652
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-8652
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>            Reporter: Edward Ribeiro
>            Assignee: Edward Ribeiro
>              Labels: cql3
>             Fix For: 2.1.2
>
>         Attachments: batch-exception.patch
>
>
> When a Keyspace or Column Family is dropped, Cassandra should evict the cached prepared statements that reference that keyspace and/or table as partially solved by the issue https://issues.apache.org/jira/browse/CASSANDRA-7566. 
> Unfortunately, when it's a BATCH prepared statement it is not being evicted from the cache. Executing the BATCH statement after a drop of KS/CF, and subsequent recreation of KS/CF with same name, should NOT retrieve them from cache, or else the batch prepared statements will throw an error like {{java.lang.IllegalArgumentException: Unknown CF fd47fd00-a0d1-11e4-8be2-75ac7e9e28a5}} because the statements inside the batch statement still hold a reference to the old (pre-dropping) cf_id. 
> The attached patch solves this issue.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)