cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Loegering (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-9324) Map Mutation rejected by Cassandra: IllegalArgumentException
Date Mon, 21 Sep 2015 09:38:04 GMT


David Loegering commented on CASSANDRA-9324:

Hi Tyler,

Thanks for the explanation, but that is where the confusion is, we are not using 2.0 nodes.
 We are using 2.1 with the 2.1 generated thrift interface and it is not working.  We are not
using 2.0 nodes nor a 2.0 interface.  Wouldn’t that indicate that there is an issue with
the 2.1 interface?  Where in the 2.1 thrift interface layer do we need to make the change?
 Should this issue be reopened?

Kind Regards,


From: Tyler Hobbs (JIRA)
Sent: ‎Friday‎, ‎September‎ ‎18‎, ‎2015 ‎4‎:‎33‎ ‎PM


Tyler Hobbs commented on CASSANDRA-9324:

[~dloegering] no, collections are still supported, you just need to encode collections slightly
different when talking to 2.1 nodes vs 2.0 nodes.  With 2.0 nodes, the collection element
count and the sizes of individual collection elements should be shorts (two bytes).  With
2.1 nodes, the collection element count and sizes are ints (four bytes).

This message was sent by Atlassian JIRA

> Map Mutation rejected by Cassandra: IllegalArgumentException
> ------------------------------------------------------------
>                 Key: CASSANDRA-9324
>                 URL:
>             Project: Cassandra
>          Issue Type: Bug
>          Components: API
>         Environment: Windows 7, Cassandra 2.1.5
>            Reporter: Mark Wick
>            Assignee: Tyler Hobbs
>            Priority: Minor
> We use a collection (map<ascii,ascii>) in a CQL3 table. We write into that cql3
table using thrift mutations, from a c++ application. We are prototyping migrating from our
current Cassandra (2.0.7) to 2.1.5, and are unable to write rows to this cql3 table. We have
no problems when we remove the writes to the map column, and all other writes succeed in this
case. Cassandra is rejecting our writes and we are catching a TTransportException (no more
data to read). The below call stack is from the Cassandra instance that is rejecting the write.
> {code}
> ERROR 14:08:10 Error occurred during processing of message.
> java.lang.IllegalArgumentException: null
>         at java.nio.Buffer.limit(Unknown Source) ~[na:1.7.0_71]
>         at org.apache.cassandra.utils.ByteBufferUtil.readBytes(
>         at org.apache.cassandra.serializers.CollectionSerializer.readValue(
>         at org.apache.cassandra.serializers.MapSerializer.validateForNativeProtocol(
>         at org.apache.cassandra.serializers.CollectionSerializer.validate(
>         at org.apache.cassandra.db.marshal.AbstractType.validate(
>         at org.apache.cassandra.thrift.ThriftValidation.validateColumnData(
>         at org.apache.cassandra.thrift.ThriftValidation.validateColumnOrSuperColumn(
>         at org.apache.cassandra.thrift.ThriftValidation.validateMutation(
>         at org.apache.cassandra.thrift.CassandraServer.createMutationList(
>         at org.apache.cassandra.thrift.CassandraServer.batch_mutate(
>         at org.apache.cassandra.thrift.Cassandra$Processor$batch_mutate.getResult(
>         at org.apache.cassandra.thrift.Cassandra$Processor$batch_mutate.getResult(
>         at org.apache.thrift.ProcessFunction.process( ~[libthrift-0.9.2.jar:0.9.2]
>         at org.apache.thrift.TBaseProcessor.process( ~[libthrift-0.9.2.jar:0.9.2]
>         at org.apache.cassandra.thrift.CustomTThreadPoolServer$
>         at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [na:1.7.0_71]
>         at java.util.concurrent.ThreadPoolExecutor$ Source) [na:1.7.0_71]
>         at Source) [na:1.7.0_71]{code}

This message was sent by Atlassian JIRA

View raw message