I agree. Thanks a lot.
On 23 Jun 2015, at 15:31 , Sam Tunnicliffe
mailto:s...@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 o
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, 20
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
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.tremb...@zen-innovations.com> wrote:
> Hi,
>
> I’m using Datastax Java Driver V 2.1.6
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 replied with
server error (java.lang
