cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sylvain Lebresne (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-5138) Provide a better CQL error when table data does not conform to CQL metadata.
Date Mon, 19 Aug 2013 09:21:48 GMT


Sylvain Lebresne commented on CASSANDRA-5138:

It is not allowed to insert cells (thrift columns if you will) that do not correspond to a
declared CQL3 column no. But that's something that would qualify as wrong from a CQL3 point
of view anyway so that does is intentional. Now from your description, it's hard to say if
you were doing it wrong or if the added validation is indeed too restrictive, but at least
looking quickly at the patch again I don't see anything wrong.

Maybe can you give a simple example of what you're trying to do and doesn't work (the CQL3
schema of the CF and and example of insertion that doesn't work with cassandra-cli for instance)?

> Provide a better CQL error when table data does not conform to CQL metadata.
> ----------------------------------------------------------------------------
>                 Key: CASSANDRA-5138
>                 URL:
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 1.2.0
>         Environment: Mac OS X running 1.2
>            Reporter: Brian ONeill
>            Assignee: Sylvain Lebresne
>            Priority: Minor
>             Fix For: 2.0
>         Attachments: 5138-2.txt, 5138.txt, northpole.cql
> When you create a table via CQL, then insert into it via Thrift.  If you inadvertently
leave out a component of the column name, in CQL you receive a:
> TSocket read 0 bytes
> Server-side the following exception is logged:
> ERROR 15:19:18,016 Error occurred during processing of message.
> java.lang.ArrayIndexOutOfBoundsException: 3
> 	at org.apache.cassandra.cql3.statements.ColumnGroupMap.add(
> 	at org.apache.cassandra.cql3.statements.ColumnGroupMap.access$200(
> 	at org.apache.cassandra.cql3.statements.ColumnGroupMap$Builder.add(
> 	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.QueryProcessor.processStatement(
> 	at org.apache.cassandra.cql3.QueryProcessor.process(
> 	at org.apache.cassandra.thrift.CassandraServer.execute_cql3_query(
> 	at org.apache.cassandra.thrift.Cassandra$Processor$execute_cql3_query.getResult(
> 	at org.apache.cassandra.thrift.Cassandra$Processor$execute_cql3_query.getResult(
> 	at org.apache.thrift.ProcessFunction.process(
> 	at org.apache.thrift.TBaseProcessor.process(
> 	at org.apache.cassandra.thrift.CustomTThreadPoolServer$
> 	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(
> 	at java.util.concurrent.ThreadPoolExecutor$
> 	at
> I'll submit a schema, and steps to reproduce.

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:

View raw message