cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Nicolas Lalevée (JIRA) <>
Subject [jira] [Created] (CASSANDRA-6966) Errors with Super Columns, mixup of 1.2 and 2.0
Date Tue, 01 Apr 2014 11:28:17 GMT
Nicolas Lalevée created CASSANDRA-6966:

             Summary: Errors with Super Columns, mixup of 1.2 and 2.0
                 Key: CASSANDRA-6966
             Project: Cassandra
          Issue Type: Bug
            Reporter: Nicolas Lalevée

On our test cluster, we tried a upgrade of Cassandra from 1.2.11 to 2.0.6. During the time
we were running with 2 different versions of cassandra, there was errors in the logs:

ERROR [WRITE-/] 2014-03-19 11:23:27,523 (line 234) error
writing to /
java.lang.RuntimeException: Cannot convert filter to old super column format. Update all nodes
to Cassandra 2.0 first.
       at org.apache.cassandra.db.SuperColumns.sliceFilterToSC(
       at org.apache.cassandra.db.SuperColumns.filterToSC(
       at org.apache.cassandra.db.ReadCommandSerializer.serializedSize(
       at org.apache.cassandra.db.ReadCommandSerializer.serializedSize(

I confirm we do have old style super columns which were designed when cassandra was 1.0.x.

Since in our test cluster the replication factor is 1, I can see errors on the client side,
since 1 node among 2 was down. So I don't know for sure if this error in cassandra affected
the client, the time frame is too short to be sure from the logs.

This message was sent by Atlassian JIRA

View raw message