You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@cassandra.apache.org by Dwight Smith <Dw...@alcatel-lucent.com> on 2010/10/28 08:19:08 UTC
Question regarding support of batch_mutate + delete + slice predicate
Investigation of this combination led to the following:
http://cassandra-user-incubator-apache-org.3065146.n2.nabble.com/batch-m
utate-deletion-slice-range-predicate-unsupported-td5048309.html
Are there plans (6.x or 7) to support this?
Thanks
-------------------------------------------------------------------------------------------------------------------
CONFIDENTIALITY NOTICE: This e-mail and any files attached may contain confidential and proprietary information of Alcatel-Lucent and/or its affiliated entities. Access by the intended recipient only is authorized. Any liability arising from any party acting, or refraining from acting, on any information contained in this e-mail is hereby excluded. If you are not the intended recipient, please notify the sender immediately, destroy the original transmission and its attachments and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Copyright in this e-mail and any attachments belongs to Alcatel-Lucent and/or its affiliated entities.
Re: Question regarding support of batch_mutate + delete + slice predicate
Posted by Jonathan Ellis <jb...@gmail.com>.
It's unscheduled (https://issues.apache.org/jira/browse/CASSANDRA-494,
as you noted) because there's the obvious workaround of performing a
slice and then deleting each column in the slice. It could happen
during a 0.7 release since it wouldn't require API changes. 0.6 is
basically bugfix-only at this point.
On Thu, Oct 28, 2010 at 1:19 AM, Dwight Smith
<Dw...@alcatel-lucent.com> wrote:
> Investigation of this combination led to the following:
>
>
>
>
> http://cassandra-user-incubator-apache-org.3065146.n2.nabble.com/batch-mutate-deletion-slice-range-predicate-unsupported-td5048309.html
>
>
>
> Are there plans (6.x or 7) to support this?
>
>
>
> Thanks
>
>
>
> CONFIDENTIALITY NOTICE: This e-mail and any files attached may contain
> confidential and proprietary information of Alcatel-Lucent and/or its
> affiliated entities. Access by the intended recipient only is authorized.
> Any liability arising from any party acting, or refraining from acting, on
> any information contained in this e-mail is hereby excluded. If you are not
> the intended recipient, please notify the sender immediately, destroy the
> original transmission and its attachments and do not disclose the contents
> to any other person, use it for any purpose, or store or copy the
> information in any medium. Copyright in this e-mail and any attachments
> belongs to Alcatel-Lucent and/or its affiliated entities.
--
Jonathan Ellis
Project Chair, Apache Cassandra
co-founder of Riptano, the source for professional Cassandra support
http://riptano.com
Re: Question regarding support of batch_mutate + delete + slice predicate
Posted by Gary Dusbabek <gd...@gmail.com>.
The main difficulty is that row mutations are currently represented
only in terms of individual columns. This has implications in the way
the transaction is carried out and represented in the commit log.
Introducing deletable slices is doable, but keeping it within the
semantics of column family operations turns out to be complicated by
our existing implementation. (Read as: touches lots of code.)
Gary.
On Thu, Oct 28, 2010 at 01:19, Dwight Smith
<Dw...@alcatel-lucent.com> wrote:
> Investigation of this combination led to the following:
>
>
>
>
> http://cassandra-user-incubator-apache-org.3065146.n2.nabble.com/batch-mutate-deletion-slice-range-predicate-unsupported-td5048309.html
>
>
>
> Are there plans (6.x or 7) to support this?
>
>
>
> Thanks
>
>
>
> CONFIDENTIALITY NOTICE: This e-mail and any files attached may contain
> confidential and proprietary information of Alcatel-Lucent and/or its
> affiliated entities. Access by the intended recipient only is authorized.
> Any liability arising from any party acting, or refraining from acting, on
> any information contained in this e-mail is hereby excluded. If you are not
> the intended recipient, please notify the sender immediately, destroy the
> original transmission and its attachments and do not disclose the contents
> to any other person, use it for any purpose, or store or copy the
> information in any medium. Copyright in this e-mail and any attachments
> belongs to Alcatel-Lucent and/or its affiliated entities.
RE: Question regarding support of batch_mutate + delete + slice predicate
Posted by Dwight Smith <Dw...@alcatel-lucent.com>.
Aaron
This did the trick - thanks.
From: aaron morton [mailto:aaron@thelastpickle.com]
Sent: Thursday, October 28, 2010 3:23 AM
To: user@cassandra.apache.org
Subject: Re: Question regarding support of batch_mutate + delete + slice
predicate
I cannot see anything in jira scheduled for 0.7 or 0.8 . Gary may be
able to shed some light on it.
There is a comment at the bottom of CASSANDRA-293 "Range operations
cannot be made to work with the existing implementation of hinted
handoff. Further, they were a bad fit for the transactional units in
cassandra (column family ops)." which links to the CASSANDRA-494 .
You can still send a SlicePredicate into the deletion, is just only
supports column_names. You can also send a null SlicePredicate to delete
and a super column or an entire row.
Hope that helps.
Aron
On 28 Oct 2010, at 19:19, Dwight Smith wrote:
Investigation of this combination led to the following:
http://cassandra-user-incubator-apache-org.3065146.n2.nabble.com/batch-m
utate-deletion-slice-range-predicate-unsupported-td5048309.html
Are there plans (6.x or 7) to support this?
Thanks
CONFIDENTIALITY NOTICE: This e-mail and any files attached may contain
confidential and proprietary information of Alcatel-Lucent and/or its
affiliated entities. Access by the intended recipient only is
authorized. Any liability arising from any party acting, or refraining
from acting, on any information contained in this e-mail is hereby
excluded. If you are not the intended recipient, please notify the
sender immediately, destroy the original transmission and its
attachments and do not disclose the contents to any other person, use it
for any purpose, or store or copy the information in any medium.
Copyright in this e-mail and any attachments belongs to Alcatel-Lucent
and/or its affiliated entities.
-------------------------------------------------------------------------------------------------------------------
CONFIDENTIALITY NOTICE: This e-mail and any files attached may contain confidential and proprietary information of Alcatel-Lucent and/or its affiliated entities. Access by the intended recipient only is authorized. Any liability arising from any party acting, or refraining from acting, on any information contained in this e-mail is hereby excluded. If you are not the intended recipient, please notify the sender immediately, destroy the original transmission and its attachments and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Copyright in this e-mail and any attachments belongs to Alcatel-Lucent and/or its affiliated entities.
Re: Question regarding support of batch_mutate + delete + slice predicate
Posted by aaron morton <aa...@thelastpickle.com>.
I cannot see anything in jira scheduled for 0.7 or 0.8 . Gary may be able to shed some light on it.
There is a comment at the bottom of CASSANDRA-293 "Range operations cannot be made to work with the existing implementation of hinted handoff. Further, they were a bad fit for the transactional units in cassandra (column family ops)." which links to the CASSANDRA-494 .
You can still send a SlicePredicate into the deletion, is just only supports column_names. You can also send a null SlicePredicate to delete and a super column or an entire row.
Hope that helps.
Aron
On 28 Oct 2010, at 19:19, Dwight Smith wrote:
> Investigation of this combination led to the following:
>
> http://cassandra-user-incubator-apache-org.3065146.n2.nabble.com/batch-mutate-deletion-slice-range-predicate-unsupported-td5048309.html
>
> Are there plans (6.x or 7) to support this?
>
> Thanks
>
>
>
> CONFIDENTIALITY NOTICE: This e-mail and any files attached may contain confidential and proprietary information of Alcatel-Lucent and/or its affiliated entities. Access by the intended recipient only is authorized. Any liability arising from any party acting, or refraining from acting, on any information contained in this e-mail is hereby excluded. If you are not the intended recipient, please notify the sender immediately, destroy the original transmission and its attachments and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Copyright in this e-mail and any attachments belongs to Alcatel-Lucent and/or its affiliated entities.