cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nate McCall (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-7910) wildcard prepared statements are incorrect after a column is added to the table
Date Wed, 26 Aug 2015 17:30:46 GMT


Nate McCall commented on CASSANDRA-7910:

Pretty sure this issue in conjunction with the changes introduced in CASSANDRA-9532 is triggering
the following error after an {{2.0.13}} to {{2.0.16}} upgrade on one node of a six node cluster:

ERROR [Native-Transport-Requests:11] 2015-07-29 18:00:50,344 (line 403) Unexpected
exception during request; channel = [id: 0x599799a6, /[redacted]:38306 => /[redacted]:9042]
at org.apache.cassandra.cql3.ResultSet.addRow(
at org.apache.cassandra.cql3.statements.Selection$
at org.apache.cassandra.cql3.statements.SelectStatement.process(
at org.apache.cassandra.cql3.statements.SelectStatement.processResults(
at org.apache.cassandra.cql3.statements.SelectStatement.execute(
at org.apache.cassandra.cql3.statements.SelectStatement.execute(
at org.apache.cassandra.cql3.statements.SelectStatement.execute(
at org.apache.cassandra.cql3.QueryProcessor.processStatement(
at org.apache.cassandra.cql3.QueryProcessor.process(
at org.apache.cassandra.transport.messages.QueryMessage.execute(
at org.apache.cassandra.transport.Message$Dispatcher.messageReceived(
at org.jboss.netty.handler.execution.ChannelUpstreamEventRunnable.doRun(
at java.util.concurrent.ThreadPoolExecutor.runWorker(
at java.util.concurrent.ThreadPoolExecutor$

Note that we passed the statement parsing phase and made it all the way down into an assertion
error on the number of returned columns vs. what metadata feels should be there. The rest
of the cluster was moved up {{2.0.15}} (after some bisecting brought up the scope of CASSANDRA-9532)
and has been running w/o issue. The one node is still running at {{2.0.16}} with transports
off so we can gather some debugging information with a custom build we just put up (for which
we'll enable binary for a bit to capture samples).

Given the impedance mismatch between these two issues and versions, I'm putting this up here
for posterity more than looking for a re-open. I'll update if we nail down a specific case
that can easily produce the error and provide a work-around (most likely not using {{SELECT
*...}} as previously mentioned). If we can destill something into a patch, we'll create a
new issue and put it there. 

> wildcard prepared statements are incorrect after a column is added to the table
> -------------------------------------------------------------------------------
>                 Key: CASSANDRA-7910
>                 URL:
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>            Reporter: Oded Peer
>            Assignee: Tyler Hobbs
>            Priority: Minor
>              Labels: client-impacting
>             Fix For: 2.1.3
>         Attachments: 7910-2.1.txt, 7910-trunk.txt,
> 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

View raw message