cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Olivier Michallat (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-7910) wildcard prepared statements are incorrect after a column is added to the table
Date Wed, 25 Nov 2015 13:51:11 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-7910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15026795#comment-15026795
] 

Olivier Michallat commented on CASSANDRA-7910:
----------------------------------------------

There's still an issue if multiple clients are connected to the same host. The first client
to execute the query after the cache was invalidated will receive an UNPREPARED response,
re-prepare, and update its local metadata. But other clients might miss it entirely (the MD5
hasn't changed), and they will keep using their old metadata.

> wildcard prepared statements are incorrect after a column is added to the table
> -------------------------------------------------------------------------------
>
>                 Key: CASSANDRA-7910
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-7910
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Oded Peer
>            Assignee: Tyler Hobbs
>            Priority: Minor
>              Labels: client-impacting
>             Fix For: 2.1.3
>
>         Attachments: 7910-2.1.txt, 7910-trunk.txt, PreparedStatementAfterAddColumnTest.java
>
>
> 1. Prepare a statement with a wildcard in the select clause.
> 2. Alter the table - add a column
> 3. execute the prepared statement
> Expected result - get all the columns including the new column
> Actual result - get the columns except the new column
> Attached a test using cassandra-unit



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

Mime
View raw message