Thank you both very much, Erick and Steve.
Steve,
1. You are right on the target. I realized it later last week and did
additional tests. I am in the process summarizing it and I am going to put
it here as a comparison reference for others.
2. It is good to know.
3. Yes, I am using EBS. I under
A few observations from what you've said so far:
1) IN clauses in CQL can have performance impact by including sets of keys
that are spread across the cluster.
2) We previously used m3.large instances in our cluster and would see
occasional read timeouts even at CL.ONE. We upgraded to i2.xlarge w
(docs AT datastax.com added to the bcc: for their information.)
On Fri, May 1, 2015 at 11:15 AM, Saurabh Sethi
wrote:
> Apache’s Cassandra code validates the keyspace name length for max 48
> characters whereas Datastax’s documentation says keyspace name should be 32
> or fewer characters.
>
> W
This article explains when it's OK to use secondary indexes in Cassandra:
http://www.wentnet.com/blog/?p=77
PS: the article is from 2013, so it can be outdated by now.. but at least
it should give you some preliminary background on the topic.
2015-04-29 16:44 GMT-03:00 Robert Coli :
> On Wed, Ap
