Probably not a great idea unless you're using it sparingly. Using LWTs
without knowing all the caveats is likely to lead to terrible cluster
performance.
On Wed, Sep 11, 2019, 10:59 PM A wrote:
> Is it ok if I do this?
>
> ... where email = em AND company_id = id IF EXISTS
>
>
>
>
>
> Sent fr
Is it ok if I do this?
... where email = em AND company_id = id IF EXISTS
Sent from Yahoo Mail for iPhone
On Wednesday, September 11, 2019, 9:08 PM, JOHN, BIBIN wrote:
#yiv9726893009 #yiv9726893009 -- _filtered #yiv9726893009 {panose-1:2 4 5 3 5 4
6 3 2 4;} _filtered #yiv9726893009 {font-
Good idea. Tried that and it doesn’t add anything to the existing table, which
exists
Sent from Yahoo Mail for iPhone
On Wednesday, September 11, 2019, 9:08 PM, JOHN, BIBIN wrote:
#yiv9726893009 #yiv9726893009 -- _filtered #yiv9726893009 {panose-1:2 4 5 3 5 4
6 3 2 4;} _filtered #yiv972
Use if exists clause.
UPDATE table
SET column ='something'
WHERE key = ‘value’ IF EXISTS;
From: A
Sent: Wednesday, September 11, 2019 11:05 PM
To: User cassandra.apache.org
Subject: Update/where statement Adds Row
I have an update statement that has a where clause with the primary key
(em
I have an update statement that has a where clause with the primary key
(email,companyid).
When executed it always creates a new row. It’s like it’s not finding the
existing row with the primary key.
I’m using Cassandra-driver.
What am I doing wrong? I don’t want a new row. Why doesn’t it seem to
Pardon the convoluted scenario, but we face some pretty ridiculous
infrastructure restrictions.
datacenter DC1: nodes containing many years of data written before
2019-09-01 (for example)
datacenter DC2: nodes containing data written after 2019-09-01
The idea is that these are independent cluste
-- Forwarded message -
From: Hossein Ghiyasi Mehr
Date: Sun, Sep 8, 2019 at 11:38 AM
Subject: Cassandra Export error in COPY command
To:
Hi all members,
I want to export (pk, another_int_column) from single node using COPY
command. But after about 1h 45m, I've got a lot of read
