[jira] [Comment Edited] (CASSANDRA-7047) TriggerExecutor should group mutations by row key

["Sergio Bossa (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/CASSANDRA-7047?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13974756#comment-13974756 ] 

Sergio Bossa edited comment on CASSANDRA-7047 at 4/19/14 7:32 AM:
------------------------------------------------------------------

First two cases have been a miss by my side.
Third case was intentional, as I preferred to keep mutations from different triggers on different input mutations separate. If you want to merge them as well, I'm ok.
I'll have a look ASAP.


was (Author: sbtourist):
First two cases have been a miss by my side.
Third case was intentional, as I preferred to keep mutations from different triggers separated.
If you want to merge them as well, I'm ok.
I'll have a look ASAP.

> TriggerExecutor should group mutations by row key
> -------------------------------------------------
>
>                 Key: CASSANDRA-7047
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-7047
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>            Reporter: Sergio Bossa
>            Assignee: Sergio Bossa
>         Attachments: 7047-v2.txt, 7047-v3.txt, CASSANDRA-7047.patch
>
>
> TriggerExecutor doesn't currently group mutations returned by triggers even if belonging to the same row key: while harmful per se (at least, I think so), this is definitely a performance problem, because each mutation is a *cluster* mutation, generating more network traffic, more disk IO and more index calls (if present).



--
This message was sent by Atlassian JIRA
(v6.2#6252)