You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@cassandra.apache.org by "T Jake Luciani (JIRA)" <ji...@apache.org> on 2015/11/24 15:00:12 UTC

[jira] [Updated] (CASSANDRA-10060) Reuse TemporalRow when updating multiple MaterializedViews

     [ https://issues.apache.org/jira/browse/CASSANDRA-10060?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

T Jake Luciani updated CASSANDRA-10060:
---------------------------------------
    Component/s: Coordination

> Reuse TemporalRow when updating multiple MaterializedViews
> ----------------------------------------------------------
>
>                 Key: CASSANDRA-10060
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-10060
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Coordination
>            Reporter: T Jake Luciani
>            Assignee: T Jake Luciani
>             Fix For: 3.0 beta 2
>
>
> If a table has 5 associated MVs the current logic reads the existing row for the incoming mutation 5 times. 
> If we reuse the data from the first MV update we can cut out any further reads.
> We know the existing data isn't changing because we are holding a lock on the partition.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)