[
https://issues.apache.org/jira/browse/CASSANDRA-5304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13646478#comment-13646478
]
Sylvain Lebresne commented on CASSANDRA-5304:
---------------------------------------------
bq. Bulk-modification is really best left to things like Hadoop
As a side note, that kind of modification-by-2ndary index could also be used
for updating/deleting selected CQL3 rows within one partition (within a "wide
row"), in which case Hadoop is definitively overkill (and likely way more
inefficient), and at least some have suggested that this was common-ish
(CASSANDRA-5527).
Not to suggest that we re-open this necessarily, I still somewhat stand by
"maybe it's better to let user do it client-side and be aware of what that
involves", but just wanted to add some color.
> Support 2ndary indexed columns in UPDATE and DELETE
> ---------------------------------------------------
>
> Key: CASSANDRA-5304
> URL: https://issues.apache.org/jira/browse/CASSANDRA-5304
> Project: Cassandra
> Issue Type: Wish
> Components: Core
> Affects Versions: 1.2.2
> Reporter: Joachim Haagen Skeie
> Priority: Minor
>
> I have a Column Family with the following index:
> CREATE INDEX live_stat_is_calculated ON live_statistics (iscalculated)
> Then, I would like to delete records based on this index via CQL3 query:
> delete from live_statistics where iscalculated = true;
> But Cassandra returns the following error:
> PRIMARY KEY part iscalculated found in SET part
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
