cassandra-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jean Tremblay <jean.tremb...@zen-innovations.com>
Subject Re: Datastax Java Driver vs Cassandra 2.1.7
Date Tue, 23 Jun 2015 13:35:13 GMT
I agree. Thanks a lot.
On 23 Jun 2015, at 15:31 , Sam Tunnicliffe <sam@beobal.com<mailto:sam@beobal.com>>
wrote:

Although amending the query is a workaround for this (and duplicating the columns in the selection
is not something I imagine one would deliberately do), this is still an ugly regression, so
I've opened https://issues.apache.org/jira/browse/CASSANDRA-9636 to fix it.

Thanks,
Sam

On Tue, Jun 23, 2015 at 1:52 PM, Jean Tremblay <jean.tremblay@zen-innovations.com<mailto:jean.tremblay@zen-innovations.com>>
wrote:
Hi Sam,

You have a real good gut feeling.
I went to see the query that I used since many months… which was working…. but obviously
there is something wrong with it.
The problem with it was *simply* that I placed twice the same field in the select. I corrected
in my code and now I don’t have the error with 2.1.7.

This provocated the error on the nodes:
ERROR [SharedPool-Worker-1] 2015-06-23 10:56:01,186 Message.java:538 - Unexpected exception
during request; channel = [id: 0x5e809aa1, /192.168.2.8:49581<http://192.168.2.8:49581/>
=> /192.168.2.201:9042<http://192.168.2.201:9042/>]
java.lang.AssertionError: null
at org.apache.cassandra.cql3.ResultSet.addRow(ResultSet.java:63) ~[apache-cassandra-2.1.7.jar:2.1.7]
at org.apache.cassandra.cql3.statements.Selection$ResultSetBuilder.newRow(Selection.java:347)
~[apache-cassandra-2.1.7.jar:2.1.7]

I can also reproduce the error on cqlsh:

cqlsh> select c1, p1, yyyymm, c2, iq, iq from ds.t1 where type='D' and c1=1 and yyyymm>=201401
and yyyymm<=201402 and p1='01';
ServerError: <ErrorMessage code=0000 [Server error] message="java.lang.AssertionError">
cqlsh> select c1, p1, yyyymm, c2, iq  from ds.t1 where type='D' and c1=1 and yyyymm>=201401
and yyyymm<=201402 and p1='01';

 c1     | p1    | yyyymm | c2     | iq
--------+-------+--------+--------+-----------------
      1 |    01 | 201401 |      1 |   {‘XX': 97160}
…

Conclusion… my mistake. Sorry.


On 23 Jun 2015, at 13:06 , Sam Tunnicliffe <sam@beobal.com<mailto:sam@beobal.com>>
wrote:

Can you share the query that you're executing when you see the error and the schema of the
target table? It could be something related to CASSANDRA-9532.

On Tue, Jun 23, 2015 at 10:05 AM, Jean Tremblay <jean.tremblay@zen-innovations.com<mailto:jean.tremblay@zen-innovations.com>>
wrote:
Hi,

I’m using Datastax Java Driver V 2.1.6
I migrated my cluster to Cassandra V2.1.7
And now I have an error on my client that goes like:

2015-06-23 10:49:11.914  WARN 20955 --- [ I/O worker #14] com.datastax.driver.core.RequestHandler
 : /192.168.2.201:9042<http://192.168.2.201:9042/> replied with server error (java.lang.AssertionError),
trying next host.

And on the node I have an NPE

ERROR [SharedPool-Worker-1] 2015-06-23 10:56:01,186 Message.java:538 - Unexpected exception
during request; channel = [id: 0x5e809aa1, /192.168.2.8:49581<http://192.168.2.8:49581/>
=> /192.168.2.201:9042<http://192.168.2.201:9042/>]
java.lang.AssertionError: null
at org.apache.cassandra.cql3.ResultSet.addRow(ResultSet.java:63) ~[apache-cassandra-2.1.7.jar:2.1.7]
at org.apache.cassandra.cql3.statements.Selection$ResultSetBuilder.newRow(Selection.java:347)
~[apache-cassandra-2.1.7.jar:2.1.7]
at org.apache.cassandra.cql3.statements.SelectStatement.processColumnFamily(SelectStatement.java:1289)
~[apache-cassandra-2.1.7.jar:2.1.7]
at org.apache.cassandra.cql3.statements.SelectStatement.process(SelectStatement.java:1223)
~[apache-cassandra-2.1.7.jar:2.1.7]
at org.apache.cassandra.cql3.statements.SelectStatement.processResults(SelectStatement.java:299)
~[apache-cassandra-2.1.7.jar:2.1.7]
at org.apache.cassandra.cql3.statements.SelectStatement.execute(SelectStatement.java:238)
~[apache-cassandra-2.1.7.jar:2.1.7]
at org.apache.cassandra.cql3.statements.SelectStatement.execute(SelectStatement.java:67) ~[apache-cassandra-2.1.7.jar:2.1.7]
at org.apache.cassandra.cql3.QueryProcessor.processStatement(QueryProcessor.java:238) ~[apache-cassandra-2.1.7.jar:2.1.7]
at org.apache.cassandra.cql3.QueryProcessor.processPrepared(QueryProcessor.java:493) ~[apache-cassandra-2.1.7.jar:2.1.7]
at org.apache.cassandra.transport.messages.ExecuteMessage.execute(ExecuteMessage.java:134)
~[apache-cassandra-2.1.7.jar:2.1.7]
at org.apache.cassandra.transport.Message$Dispatcher.channelRead0(Message.java:439) [apache-cassandra-2.1.7.jar:2.1.7]
at org.apache.cassandra.transport.Message$Dispatcher.channelRead0(Message.java:335) [apache-cassandra-2.1.7.jar:2.1.7]
at io.netty.channel.SimpleChannelInboundHandler.channelRead(SimpleChannelInboundHandler.java:105)
[netty-all-4.0.23.Final.jar:4.0.23.Final]
at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:333)
[netty-all-4.0.23.Final.jar:4.0.23.Final]
at io.netty.channel.AbstractChannelHandlerContext.access$700(AbstractChannelHandlerContext.java:32)
[netty-all-4.0.23.Final.jar:4.0.23.Final]
at io.netty.channel.AbstractChannelHandlerContext$8.run(AbstractChannelHandlerContext.java:324)
[netty-all-4.0.23.Final.jar:4.0.23.Final]
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [na:1.8.0_45]
at org.apache.cassandra.concurrent.AbstractTracingAwareExecutorService$FutureTask.run(AbstractTracingAwareExecutorService.java:164)
[apache-cassandra-2.1.7.jar:2.1.7]
at org.apache.cassandra.concurrent.SEPWorker.run(SEPWorker.java:105) [apache-cassandra-2.1.7.jar:2.1.7]
at java.lang.Thread.run(Thread.java:745) [na:1.8.0_45]

Is there a known problem on Cassandra 2.1.7?

Thanks for your comments.

Jean




Mime
View raw message