Just to add, it works fine with Cassandra 1.x and Datastax 1.x
-Vivek
On Sat, Apr 26, 2014 at 10:02 AM, Vivek Mishra wrote:
> Yes i know. But i am not sure why is it failing, simply having Thrift jar
> and cassandra-thrift in classpath doesn't fails. But as soon as i get
> datastax one in class
Yes i know. But i am not sure why is it failing, simply having Thrift jar
and cassandra-thrift in classpath doesn't fails. But as soon as i get
datastax one in classpath, it started failing. Point is even if i am having
both in classpath, switching b/w thrift and Datastax should work.
-Vivek
On
TSocket socket = new TSocket(host, Integer.parseInt(port));
TTransport transport = new TFramedTransport(socket);
TProtocol protocol = new TBinaryProtocol(transport, true, true);
cassandra_client = new Cassandra.Client(protocol);
cassandr
Vivek,
The error you are seeing is a thrift error, but you say you are using the
Java driver which does not operate over thrift: are you perhaps trying to
connect the datastax driver to the thrift protocol port? The two protocols
are not compatible, you must connect to the native_transport_port (b
Can you share the relevant code snippet that leads to this exception?
On Fri, Apr 25, 2014 at 4:47 PM, Vivek Mishra wrote:
> datastax java driver 2.0.1
>
>
>
>
> On Sat, Apr 26, 2014 at 1:35 AM, Chris Lohfink
> wrote:
>
>> what client are you using?
>>
>> On Apr 25, 2014, at 3:01 PM, Vivek Mis
datastax java driver 2.0.1
On Sat, Apr 26, 2014 at 1:35 AM, Chris Lohfink wrote:
> what client are you using?
>
> On Apr 25, 2014, at 3:01 PM, Vivek Mishra wrote:
>
> It's a simple cql3 query to create keyspace.
>
> -Vivek
>
>
> On Sat, Apr 26, 2014 at 1:28 AM, Chris Lohfink
> wrote:
>
>> Di
what client are you using?
On Apr 25, 2014, at 3:01 PM, Vivek Mishra wrote:
> It's a simple cql3 query to create keyspace.
>
> -Vivek
>
>
> On Sat, Apr 26, 2014 at 1:28 AM, Chris Lohfink
> wrote:
> Did you send an enormous write or batch write and it wrapped? Or is your
> client trying to
It's a simple cql3 query to create keyspace.
-Vivek
On Sat, Apr 26, 2014 at 1:28 AM, Chris Lohfink wrote:
> Did you send an enormous write or batch write and it wrapped? Or is your
> client trying to use non-framed transport?
>
> Chris
>
> On Apr 25, 2014, at 2:50 PM, Vivek Mishra wrote:
>
>
Did you send an enormous write or batch write and it wrapped? Or is your
client trying to use non-framed transport?
Chris
On Apr 25, 2014, at 2:50 PM, Vivek Mishra wrote:
> This is what i am getting with Cassandra 2.0.7 with Thrift.
>
>
> Caused by: org.apache.thrift.transport.TTransportExc
This is what i am getting with Cassandra 2.0.7 with Thrift.
Caused by: org.apache.thrift.transport.TTransportException: Read a negative
frame size (-2113929216)!
at
org.apache.thrift.transport.TFramedTransport.readFrame(TFramedTransport.java:133)
at
org.apache.thrift.transport.TFramedTransport.re
Other people have expressed an interest and there's existing jira ticket for
this type if feature.
Unfortunately it hasn't gotten much traction and the tickets are basically dead
Sent from my iPhone
> On Apr 25, 2014, at 12:03 PM, Mikhail Mazursky wrote:
>
> Hello Paco,
>
> thanks for respo
Hello Paco,
thanks for response.
IMHO this is a not implemented feature in such case. Instead of fetching
whole wide row using partitioning key and filtering it on client side this
can be done on server side. In my particular case this will be more optimal
than adding secondary index. Maybe in ca
Hi,
We have a keyspace starting with an upper-case character: Visitors.
We are trying to run a map reduce job on one of the column family of this
keyspace.
To specify the keyspace it seems we have to use:
org.apache.cassandra.hadoop.
ConfigHelper.setInputColumnFamily(conf, keyspace, columnFamily)
You might want to take a peek at what’s happening in the process via strace -p
or tcpdump. I can’t remember ever waiting an hour for a node to rejoin.
On Apr 25, 2014, at 8:59 AM, Tyler Hobbs wrote:
>
> On Fri, Apr 25, 2014 at 10:43 AM, Phil Burress
> wrote:
> Thanks. I made a change to a
On Fri, Apr 25, 2014 at 10:43 AM, Phil Burress wrote:
> Thanks. I made a change to a single node and it took almost an hour to
> rejoin the cluster (go from DN to UP in nodetool status). The cluster is
> pretty much idle right now and has a very small dataset. Is that normal?
Not unless it had t
Thanks. I made a change to a single node and it took almost an hour to
rejoin the cluster (go from DN to UP in nodetool status). The cluster is
pretty much idle right now and has a very small dataset. Is that normal?
On Fri, Apr 25, 2014 at 10:08 AM, Chris Lohfink wrote:
> Yes.
>
> Some changes
Interesting. I did our 2.0.3 -> 2.0.5 upgrade by bootstrapping/joining each
node into our cluster, one at a time, then retiring the old nodes one at a
time. Maybe something specific to the 2.0.6 release?
Good to hear that you've gotten through it anyway.
Steve
On Fri, Apr 25, 2014 at 7:49 AM,
Cassandra 2.0.6
On Fri, Apr 25, 2014 at 10:31 AM, James Rothering wrote:
> What version of C* is this?
>
>
> On Fri, Apr 25, 2014 at 6:55 AM, Phil Burress wrote:
>
>> Just a follow-up on this for any interested parties. Ultimately we've
>> determined that the bootstrap/join process is broken in
What version of C* is this?
On Fri, Apr 25, 2014 at 6:55 AM, Phil Burress wrote:
> Just a follow-up on this for any interested parties. Ultimately we've
> determined that the bootstrap/join process is broken in Cassandra. We ended
> up creating an entirely new cluster and migrating the data.
>
>
Yes.
Some changes you can manually have take affect without a restart (ie
compactionthroughput, things settable from jmx). There is also config changes
you cant really make like switching the snitch and such without a big todo.
---
Chris
On Apr 25, 2014, at 8:53 AM, Phil Burress wrote:
> If
Just a follow-up on this for any interested parties. Ultimately we've
determined that the bootstrap/join process is broken in Cassandra. We ended
up creating an entirely new cluster and migrating the data.
On Mon, Apr 21, 2014 at 10:32 AM, Phil Burress wrote:
> The new node has managed to stay u
If I wanted to make a configuration change to a single node in a cluster,
what is the recommended approach for doing that? Is it ok to just stop that
instance, make the change and then restart it?
Hi Mikhail
It is not a bug/not implemented feature and you are not doing nothing wrong.
As you can check on the documentation you can only filter on a key name or a
column that has a secondary index created on it:
http://www.datastax.com/documentation/cql/3.1/cql/cql_reference/select_r.html
F
Hello all,
I have the following schema:
CREATE TABLE my_table (
a varchar,
b varchar,
c int,
d varchar,
e uuid,
PRIMARY KEY ((a, b), c, d)
)
SELECT * FROM my_table WHERE a=? AND b=? AND e=? ALLOW FILTERING
The query above gives me the following exception message:
com.da
24 matches
Mail list logo
