You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Aleksey Yeschenko (JIRA)" <ji...@apache.org> on 2014/04/18 04:25:16 UTC

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

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

Aleksey Yeschenko commented on CASSANDRA-7047:
----------------------------------------------

Oh, well. Cleaned up TriggerExecutorTest, and only then realized that something is wrong (by TriggerExecutorTest diff being all green and lacking the license header).

We already have TriggersTest.java. Can you move the tests there? (and rewrite them to match the style of the tests there, too?)

Thanks.

> 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, 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)