cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tyler Hobbs (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-5287) Composite comparators for super CFs broken in 1.2
Date Wed, 27 Feb 2013 19:31:12 GMT

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

Tyler Hobbs commented on CASSANDRA-5287:
----------------------------------------

The patch seems fine to me, but I'm not terribly familiar with this area of the code.  With
it applied, all of the pycassa and phpcassa tests pass, and they cover this pretty well.
                
> Composite comparators for super CFs broken in 1.2
> -------------------------------------------------
>
>                 Key: CASSANDRA-5287
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-5287
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 1.2.0
>            Reporter: Tyler Hobbs
>            Assignee: Sylvain Lebresne
>             Fix For: 1.2.3
>
>         Attachments: 5287-pycassa-repro.py, 5287.txt
>
>
> In Cassandra 1.2.0 through 1.2.2, attempting to insert data into a super column family
with a CompositeType comparator results in the following stacktrace:
> {noformat}
> ERROR 14:56:49,920 Error occurred during processing of message.
> java.lang.IllegalArgumentException
> 	at java.nio.Buffer.limit(Buffer.java:249)
> 	at org.apache.cassandra.db.marshal.AbstractCompositeType.getBytes(AbstractCompositeType.java:51)
> 	at org.apache.cassandra.db.marshal.AbstractCompositeType.getWithShortLength(AbstractCompositeType.java:60)
> 	at org.apache.cassandra.db.marshal.AbstractCompositeType.split(AbstractCompositeType.java:126)
> 	at org.apache.cassandra.config.CFMetaData.getColumnDefinitionFromColumnName(CFMetaData.java:920)
> 	at org.apache.cassandra.thrift.ThriftValidation.validateColumnData(ThriftValidation.java:404)
> 	at org.apache.cassandra.thrift.ThriftValidation.validateColumnOrSuperColumn(ThriftValidation.java:287)
> 	at org.apache.cassandra.thrift.ThriftValidation.validateMutation(ThriftValidation.java:343)
> 	at org.apache.cassandra.thrift.CassandraServer.createMutationList(CassandraServer.java:704)
> 	at org.apache.cassandra.thrift.CassandraServer.batch_mutate(CassandraServer.java:752)
> 	at org.apache.cassandra.thrift.Cassandra$Processor$batch_mutate.getResult(Cassandra.java:3622)
> 	at org.apache.cassandra.thrift.Cassandra$Processor$batch_mutate.getResult(Cassandra.java:3610)
> 	at org.apache.thrift.ProcessFunction.process(ProcessFunction.java:32)
> 	at org.apache.thrift.TBaseProcessor.process(TBaseProcessor.java:34)
> 	at org.apache.cassandra.thrift.CustomTThreadPoolServer$WorkerProcess.run(CustomTThreadPoolServer.java:199)
> 	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
> 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
> 	at java.lang.Thread.run(Thread.java:662)
> {noformat}
> Client-side, you'll just see "{{TTransportException: TSocket read 0 bytes}}".
> Cassandra 1.1 doesn't have the same problem.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message