At Orange portails we are presently testing Cassandra 1.2.0 beta/rc
with Java 7, and presnetly we have no issues
2012/12/22 Brian Tarbox tar...@cabotresearch.com:
What I saw in all cases was
a) set JAVA_HOME to java7, run program fail
b) set JAVA_HOME to java6, run program success
I should
This what versions are supported is kinda up to you for example earlier
versions of jdk now have bugs. I have a version of java 1.6.0_23 I believe
that will not even start with the latest cassandra releases. Likewise
people suggest not running the newest ones 1.7.0 because they have not
tested it.
Unfortunately one of the first command everyone needs to use to use to work
with cassandra changes very often.
You can use
cqlsh help create_keyspace;
But some times even the documentation is not in line.
Using this permutation of goodness:
cqlsh 2.3.0 | Cassandra 1.2.0-beta2-SNAPSHOT | CQL
Agreed. I actually flip between cli and cqlsh these days.
Only tables created with COMPACT STORAGE are visible to cassandra-cli (in fact
visible to any thrift based client).
This article helps http://www.datastax.com/dev/blog/cql3-for-cassandra-experts
Is there still a way to have composite
First, the non helpful advice, I strongly suggest changing the data model so
you do not have 100MB+ rows. They will make life harder.
Write request latency is about 900 microsecs, read request
latency
is about 4000 microsecs.
4 milliseconds to
Yup, this is pretty explicit when listing from the cli. Great to know that
composite row keys are coming, lookikng forward to it
On Sun, Dec 23, 2012 at 8:25 PM, aaron morton aa...@thelastpickle.comwrote:
Agreed. I actually flip between cli and cqlsh these days.
Only tables created with
