Re: Fwd: Re: cassandra update vs insert + delete

[Rahul Singh]

Soft delete = logical delete - which is an update.

An update doesnt create a tombstone . It appends to the sstable,and when they 
are compacted, the latest write is what is seen as the definitive data.

 A tombstone by definition is an update which tells C* to remove the value that 
was there before, but doesn’t do it immediately .


On May 28, 2018, 2:32 AM -0400, onmstester onmstester , 
wrote:
> How update is working underneath?
> Does it create a new row (because i'm changing a column of partition key) and 
> add a tombstone to the old row?
>
> Sent using Zoho Mail
>
>
>  Forwarded message 
> From : Jonathan Haddad 
> To : 
> Date : Mon, 28 May 2018 00:07:36 +0430
> Subject : Re: cassandra update vs insert + delete
>  Forwarded message 
>
> > What is a “soft delete”?
> >
> > My 2 cents, if you want to update some information just update it. There’s 
> > no need to overthink it.
> >
> > Batches are good if they’re constrained to a single partition, not so hot 
> > otherwise.
> >
> >
> > On Sun, May 27, 2018 at 8:19 AM Rahul Singh  
> > wrote:
> >
> > --
> > Jon Haddad
> > http://www.rustyrazorblade.com
> > twitter: rustyrazorblade
> > > Deletes create tombstones — not really something to consider. Better to 
> > > add / update or insert data and do a soft delete on old data and apply a 
> > > TTL to remove it at a future time.
> > >
> > > --
> > > Rahul Singh
> > > rahul.si...@anant.us
> > >
> > > Anant Corporation
> > >
> > > On May 27, 2018, 5:36 AM -0400, onmstester onmstester 
> > > , wrote:
> > >
> > > > Hi
> > > > I want to load all rows from many partitions and change a column value 
> > > > in each row, which of following ways is better concerning disk space 
> > > > and performance?
> > > > 1. create a update statement for every row and batch update for each 
> > > > partitions
> > > > 2. create an insert statement for every row and batch insert for each 
> > > > partition, then run a single statement to delete the whole old partition
> > > >
> > > > Thanks in advance
> > > >
> > > > Sent using Zoho Mail
> > > >
>
>

答复: 答复: Re: cassandra update vs insert + delete

[Xiangfei Ni]

It is not possible to update the primary key.

Best Regards,

倪项菲/ David Ni
中移德电网络科技有限公司
Virtue Intelligent Network Ltd, co.
Add: 2003,20F No.35 Luojia creative city,Luoyu Road,Wuhan,HuBei
Mob: +86 13797007811|Tel: + 86 27 5024 2516

发件人: onmstester onmstester <onmstes...@zoho.com>
发送时间: 2018年5月28日 14:42
收件人: user <user@cassandra.apache.org>
主题: Fwd: 答复: Re: cassandra update vs insert + delete

It seems that i can't update a part of primary key in cqlsh update:
message "PRIMARY Key part column found in SET part"


Sent using Zoho Mail<https://www.zoho.com/mail/>


 Forwarded message 
From : Xiangfei Ni <xiangfei...@cm-dt.com<mailto:xiangfei...@cm-dt.com>>
To : 
"user@cassandra.apache.org<mailto:user@cassandra.apache.org>"<user@cassandra.apache.org<mailto:user@cassandra.apache.org>>
Date : Mon, 28 May 2018 11:04:06 +0430
Subject : 答复: Re: cassandra update vs insert + delete
 Forwarded message 

Yes, you are correct.

Best Regards,

倪项菲/ David Ni
中移德电网络科技有限公司
Virtue Intelligent Network Ltd, co.
Add: 2003,20F No.35 Luojia creative city,Luoyu Road,Wuhan,HuBei
Mob: +86 13797007811|Tel: + 86 27 5024 2516

发件人: onmstester onmstester <onmstes...@zoho.com<mailto:onmstes...@zoho.com>>
发送时间: 2018年5月28日 14:33
收件人: user <user@cassandra.apache.org<mailto:user@cassandra.apache.org>>
主题: Fwd: Re: cassandra update vs insert + delete

How update is working underneath?
Does it create a new row (because i'm changing a column of partition key) and 
add a tombstone to the old row?


Sent using Zoho Mail<https://www.zoho.com/mail/>


 Forwarded message 
From : Jonathan Haddad <j...@jonhaddad.com<mailto:j...@jonhaddad.com>>
To : <user@cassandra.apache.org<mailto:user@cassandra.apache.org>>
Date : Mon, 28 May 2018 00:07:36 +0430
Subject : Re: cassandra update vs insert + delete
 Forwarded message 

What is a “soft delete”?

My 2 cents, if you want to update some information just update it. There’s no 
need to overthink it.

Batches are good if they’re constrained to a single partition, not so hot 
otherwise.


On Sun, May 27, 2018 at 8:19 AM Rahul Singh 
<rahul.xavier.si...@gmail.com<mailto:rahul.xavier.si...@gmail.com>> wrote:

--
Jon Haddad
http://www.rustyrazorblade.com
twitter: rustyrazorblade
Deletes create tombstones — not really something to consider. Better to add / 
update or insert data and do a soft delete on old data and apply a TTL to 
remove it at a future time.

--
Rahul Singh
rahul.si...@anant.us<mailto:rahul.si...@anant.us>

Anant Corporation

On May 27, 2018, 5:36 AM -0400, onmstester onmstester 
<onmstes...@zoho.com<mailto:onmstes...@zoho.com>>, wrote:

Hi
I want to load all rows from many partitions and change a column value in each 
row, which of following ways is better concerning disk space and performance?
1. create a update statement for every row and batch update for each partitions
2. create an insert statement for every row and batch insert for each 
partition, then run a single statement to delete the whole old partition

Thanks in advance


Sent using Zoho Mail<https://www.zoho.com/mail/>

Fwd: 答复: Re: cassandra update vs insert + delete

[onmstester onmstester]

It seems that i can't update a part of primary key in cqlsh update:

message "PRIMARY Key part column found in SET part"


Sent using Zoho Mail






 Forwarded message 

>From : Xiangfei Ni xiangfei...@cm-dt.com

To : "user@cassandra.apache.org"user@cassandra.apache.org

Date : Mon, 28 May 2018 11:04:06 +0430

Subject : 答复: Re: cassandra update vs insert + delete

 Forwarded message 




Yes, you are correct.

 

Best Regards,

 

倪项菲/ David Ni

中移德电网络科技有限公司

Virtue Intelligent Network Ltd, co.

Add: 2003,20F No.35 Luojia creative city,Luoyu Road,Wuhan,HuBei

Mob: +86 13797007811|Tel: + 86 27 5024 2516


 

发件人: onmstester onmstester onmstes...@zoho.com 
 发送时间: 2018年5月28日 14:33
 收件人: user user@cassandra.apache.org
 主题: Fwd: Re: cassandra update vs insert + delete


 

How update is working underneath?


Does it create a new row (because i'm changing a column of partition key) and 
add a tombstone to the old row?


 


Sent using Zoho Mail


 


 


 Forwarded message 


>From : Jonathan Haddad j...@jonhaddad.com


To : user@cassandra.apache.org


Date : Mon, 28 May 2018 00:07:36 +0430


Subject : Re: cassandra update vs insert + delete


 Forwarded message 



 


What is a “soft delete”? 


 


My 2 cents, if you want to update some information just update it. There’s no 
need to overthink it. 


 


Batches are good if they’re constrained to a single partition, not so hot 
otherwise. 


 


 


On Sun, May 27, 2018 at 8:19 AM Rahul Singh 
rahul.xavier.si...@gmail.com wrote:


 




--


Jon Haddad


http://www.rustyrazorblade.com


twitter: rustyrazorblade




Deletes create tombstones — not really something to consider. Better to add / 
update or insert data and do a soft delete on old data and apply a TTL to 
remove it at a future time.


 


--


Rahul Singh


rahul.si...@anant.us


 


Anant Corporation




 


On May 27, 2018, 5:36 AM -0400, onmstester onmstester 
onmstes...@zoho.com, wrote:


 


Hi


I want to load all rows from many partitions and change a column value in each 
row, which of following ways is better concerning disk space and performance?


1. create a update statement for every row and batch update for each partitions


2. create an insert statement for every row and batch insert for each 
partition, then run a single statement to delete the whole old partition


 


Thanks in advance


 


Sent using Zoho Mail


 






 



 

答复: Re: cassandra update vs insert + delete

[Xiangfei Ni]

Yes, you are correct.

Best Regards,

倪项菲/ David Ni
中移德电网络科技有限公司
Virtue Intelligent Network Ltd, co.
Add: 2003,20F No.35 Luojia creative city,Luoyu Road,Wuhan,HuBei
Mob: +86 13797007811|Tel: + 86 27 5024 2516

发件人: onmstester onmstester <onmstes...@zoho.com>
发送时间: 2018年5月28日 14:33
收件人: user <user@cassandra.apache.org>
主题: Fwd: Re: cassandra update vs insert + delete

How update is working underneath?
Does it create a new row (because i'm changing a column of partition key) and 
add a tombstone to the old row?


Sent using Zoho Mail<https://www.zoho.com/mail/>


 Forwarded message 
From : Jonathan Haddad <j...@jonhaddad.com<mailto:j...@jonhaddad.com>>
To : <user@cassandra.apache.org<mailto:user@cassandra.apache.org>>
Date : Mon, 28 May 2018 00:07:36 +0430
Subject : Re: cassandra update vs insert + delete
 Forwarded message 

What is a “soft delete”?

My 2 cents, if you want to update some information just update it. There’s no 
need to overthink it.

Batches are good if they’re constrained to a single partition, not so hot 
otherwise.


On Sun, May 27, 2018 at 8:19 AM Rahul Singh 
<rahul.xavier.si...@gmail.com<mailto:rahul.xavier.si...@gmail.com>> wrote:

--
Jon Haddad
http://www.rustyrazorblade.com
twitter: rustyrazorblade
Deletes create tombstones — not really something to consider. Better to add / 
update or insert data and do a soft delete on old data and apply a TTL to 
remove it at a future time.

--
Rahul Singh
rahul.si...@anant.us<mailto:rahul.si...@anant.us>

Anant Corporation

On May 27, 2018, 5:36 AM -0400, onmstester onmstester 
<onmstes...@zoho.com<mailto:onmstes...@zoho.com>>, wrote:

Hi
I want to load all rows from many partitions and change a column value in each 
row, which of following ways is better concerning disk space and performance?
1. create a update statement for every row and batch update for each partitions
2. create an insert statement for every row and batch insert for each 
partition, then run a single statement to delete the whole old partition

Thanks in advance


Sent using Zoho Mail<https://www.zoho.com/mail/>

Fwd: Re: cassandra update vs insert + delete

[onmstester onmstester]

How update is working underneath?

Does it create a new row (because i'm changing a column of partition key) and 
add a tombstone to the old row?



Sent using Zoho Mail






 Forwarded message 

>From : Jonathan Haddad j...@jonhaddad.com

To : user@cassandra.apache.org

Date : Mon, 28 May 2018 00:07:36 +0430

Subject : Re: cassandra update vs insert + delete

 Forwarded message 




What is a “soft delete”? 



My 2 cents, if you want to update some information just update it. There’s no 
need to overthink it. 



Batches are good if they’re constrained to a single partition, not so hot 
otherwise. 





On Sun, May 27, 2018 at 8:19 AM Rahul Singh 
rahul.xavier.si...@gmail.com wrote:





-- 

Jon Haddad

http://www.rustyrazorblade.com

twitter: rustyrazorblade



Deletes create tombstones — not really something to consider. Better to add / 
update or insert data and do a soft delete on old data and apply a TTL to 
remove it at a future time.



--

 Rahul Singh

 rahul.si...@anant.us

 

 Anant Corporation





On May 27, 2018, 5:36 AM -0400, onmstester onmstester 
onmstes...@zoho.com, wrote:

 

Hi

I want to load all rows from many partitions and change a column value in each 
row, which of following ways is better concerning disk space and performance?

1. create a update statement for every row and batch update for each partitions

2. create an insert statement for every row and batch insert for each 
partition, then run a single statement to delete the whole old partition



Thanks in advance



Sent using Zoho Mail

Re: cassandra update vs insert + delete

[Jonathan Haddad]

What is a “soft delete”?

My 2 cents, if you want to update some information just update it. There’s
no need to overthink it.

Batches are good if they’re constrained to a single partition, not so hot
otherwise.


On Sun, May 27, 2018 at 8:19 AM Rahul Singh 
wrote:

> Deletes create tombstones — not really something to consider. Better to
> add / update or insert data and do a soft delete on old data and apply a
> TTL to remove it at a future time.
>
> --
> Rahul Singh
> rahul.si...@anant.us
>
> Anant Corporation
>
> On May 27, 2018, 5:36 AM -0400, onmstester onmstester ,
> wrote:
>
> Hi
> I want to load all rows from many partitions and change a column value in
> each row, which of following ways is better concerning disk space and
> performance?
> 1. create a update statement for every row and batch update for each
> partitions
> 2. create an insert statement for every row and batch insert for each
> partition, then run a single statement to delete the whole old partition
>
> Thanks in advance
>
> Sent using Zoho Mail 
>
>
> --
Jon Haddad
http://www.rustyrazorblade.com
twitter: rustyrazorblade

Re: cassandra update vs insert + delete

[Rahul Singh]

Deletes create tombstones — not really something to consider. Better to add / 
update or insert data and do a soft delete on old data and apply a TTL to 
remove it at a future time.

--
Rahul Singh
rahul.si...@anant.us

Anant Corporation

On May 27, 2018, 5:36 AM -0400, onmstester onmstester , 
wrote:
> Hi
> I want to load all rows from many partitions and change a column value in 
> each row, which of following ways is better concerning disk space and 
> performance?
> 1. create a update statement for every row and batch update for each 
> partitions
> 2. create an insert statement for every row and batch insert for each 
> partition, then run a single statement to delete the whole old partition
>
> Thanks in advance
>
> Sent using Zoho Mail
>
>

cassandra update vs insert + delete

[onmstester onmstester]

Hi 

I want to load all rows from many partitions and change a column value in each 
row, which of following ways is better concerning disk space and performance?

1. create a update statement for every row and batch update for each partitions

2. create an insert statement for every row and batch insert for each 
partition, then run a single statement to delete the whole old partition



Thanks in advance



Sent using Zoho Mail