Uploaded image for project: 'Cassandra'
  1. Cassandra
  2. CASSANDRA-8652

DROP TABLE should also drop BATCH prepared statements associated to it

Agile BoardAttach filesAttach ScreenshotVotersWatch issueWatchersCreate sub-taskConvert to sub-taskMoveLinkCloneLabelsUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Normal
    • Resolution: Fixed
    • Fix Version/s: 2.1.3
    • Component/s: None
    • Labels:
    • Severity:
      Normal
    • Since Version:

      Description

      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.

        Attachments

          Activity

            People

            • Assignee:
              eribeiro Edward Ribeiro Assign to me
              Reporter:
              eribeiro Edward Ribeiro
              Authors:
              Edward Ribeiro
              Reviewers:
              Tom Hobbs

              Dates

              • Created:
                Updated:
                Resolved:

                Issue deployment