Hi ,
I need your help & suggestions for our production issue.
Details:
--
we have 40 CF's in cassandra cluster for each datasource like below
MusicData--Keyspace
spotify_1-column family-Active
spotify_2-column family-standby
Daily we load data into this cluster using as below proc
I'm not sure if this is your issue as I have not used these triggers before but
shouldn't the invertedindex table have a different primary key than the primary
table (either f2 or f3)?
-Thunder
> On Jan 11, 2014, at 12:03 PM, Vidit Asthana wrote:
>
> I am new to cassandra and trying to run t
Hi,
I have following understanding about Cassandra read repair:
* If we write with QUORUM and read with QUORUM then we do not need to
externally (nodetool) trigger read repair.
* Since we are reading + writing with QUORUM then it is safe to set
"read_repair_chance=0 & dclocal_r
Thank you both for the answers!
Jiri Horky
On 01/10/2014 02:52 AM, Aaron Morton wrote:
> We avoid mixing versions for a long time, but we always upgrade one
> node and check the application is happy before proceeding. e.g. wait
> for 30 minutes before upgrading the others.
>
> If you snapshot be
I am new to cassandra and trying to run the trigger example provided by
cassandra on a pseudo cluster using instructions provided on
https://github.com/apache/cassandra/tree/cassandra-2.0/examples/triggers
But i am getting error: *Bad Request: Key may not be empty*
Can someone tell me if my "CR
Hi,
I know that triggers are still experimental but I want to know if they are
prod ready? If not when will it be.