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 <dwight.sm...@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
