[
https://issues.apache.org/jira/browse/CASSANDRA-7047?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sergio Bossa updated CASSANDRA-7047:
------------------------------------
Description: TriggerExecutor doesn't currently group mutations returned by
triggers even if belonging to the same row key: while harmless 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). (was: 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).)
> 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 harmless 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)
