rom 2.1 to
>> 3.2
>>
>> You need to upgrade first to C* 2.2 before migrating to C* 3.x
>>
>> For each version, read the NEWS.txt file and follow the procedure:
>>
>> From 2.1.x to 2.2.x :
>> https://github.com/apache/cassandra/blob/cassandra-2.2/NE
Hi,
I am a newbie when it comes to Cassandra administration and operation. We
have a single node cluster running 2.1 in EC2 and we are planning to move
it to better single machine instance and want to run 3.2 on that.
I installed 3.2 on the new machine and created a snapshot of the old
cluster
, 2015 at 12:53 PM, Rahul Srivastava
srivastava.robi...@gmail.com wrote:
but what if i want to fetch the value using on table then this idea might
fail
On Mon, Mar 2, 2015 at 12:46 PM, Ajaya Agrawal ajku@gmail.com wrote:
Make a table for each of the unique keys. For e.g.
If primary key
Make a table for each of the unique keys. For e.g.
If primary key for user table is user_id and you want the phone number
column to be unique then create another table wherein the primary key is
(phone_number, user_id). Before inserting to main table try to insert to
this table first with if not
It would be around April of this year. I asked the same thing in
cassaandra-dev irc channel sometime back. This is by no means an official
release date or month, just a guesstimate.
Cheers,
Ajaya
On Wed, Feb 11, 2015 at 6:49 PM, Ernesto Reinaldo Barreiro
reier...@gmail.com wrote:
Thanks for
On Sun, Feb 8, 2015 at 5:03 AM, Eric Stevens migh...@gmail.com wrote:
I'm struggling to think of a model where it makes sense to update a
primary key as a typical operation. It suggests, as Adil said, that you
may be reasoning wrong about your data model. Maybe you can explain your
problem
On Fri, Feb 6, 2015 at 7:43 PM, Adil adil.cha...@gmail.com wrote:
Hi,
it seems you are doing some thing wrong in your model, why can you go with
updating columns of key1 instead of deleting/inserting row key?
You can't update a primary key column with update statements.
Hi guys,
I want to take a row with primary key K1, rewrite it with primary key K2,
and delete the original data with key K1, atomically.
It seems like the only solution which won't have race conditions is to use
batch statement to delete the old row and insert the new one. But the
documentation
