And cql-rb is full featured when it comes to CQL3. It supports all features
of Cassandra 1.2. For some of the Cassandra 2.0 features you have to wait
for a final version of 2.0, but the current prerelease is stable and well
tested.
yours
Theo
On Wed, Mar 19, 2014 at 5:21 PM, Theo Hultberg wrote
I'm the author of cql-rb, the first one on your list. It runs in production
in systems doing tens of thousands of operations per second. cequel is an
ORM and its latest version runs on top of cql-rb.
If you decide on using cql-rb I'm happy to help you out with any problems
you might have, just ope
Bump, could anyone comment this behaviour, is it correct, or should I
create Jira task for this problems?
regards
Olek
2014-03-18 16:49 GMT+01:00 olek.stas...@gmail.com :
> Oh, one more question: what should be configuration for storing
> system_traces keyspace? Should it be replicated or stored l
I think we've found the issue!
It seems that the times on those Cassandra servers was being kept in sync by
vmware tools using the time of the vmware host machine. We have now turned
that off and are using the ntp service to keep the times in sync like we do
for our physical servers and we have no
Apologies,
this seems to be addressed in the thread :
https://groups.google.com/a/lists.datastax.com/forum/#!searchin/java-driver-user/blob$20ByteBuffer/java-driver-user/4_KegVX0teo/2OOZ8YOwtBcJ
Andy
On 19 Mar 2014, at 11:55, Andrew Cobley
mailto:a.e.cob...@dundee.ac.uk>> wrote:
Cassandra 2.0
Hi,
On our test cluster, we tried a upgrade of Cassandra from 1.22.1 to 2.0.6. It
was not straight forward so I would like to know if it is expected, so I can do
it safely on prod.
The first time we tried, the first upgrading node refused to start with this
error:
ERROR [main] 2014-03-19 10:5
Cassandra 2.0.4
I’m using blobs to save and retrieve images in cassanda. However the blob I
get back is not the blob I saved !
I’m saving to CQL like this:
byte[] b= {(byte)10,(byte)20,(byte)30};
int length=b.length;
ByteBuffer buffer =ByteBuffer.wrap(b);
Session session = cluster.connect("k
Hi,
you should set 'listen_address' to ip address of eth4.
'listen_address' is for communication between cassandra nodes (not clients).
Btw I hope you don't use NFS for commit log directory.
--
cheers
mc
On Wed, Mar 19, 2014 at 5:14 AM, Le Xu wrote:
> I'm currently using Cassandra 1.23 and
Hi,
we did something similar. We did utilize some cassandra code though and
wrote a custom commitlog reader that outputs our data into a readable form.
You can look here:
http://grepcode.com/file/repo1.maven.org/maven2/org.apache.cassandra/cassandra-all/1.1.9/org/apache/cassandra/db/commitlog
