cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "T Jake Luciani (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-10060) Reuse TemporalRow when updating multiple MaterializedViews
Date Thu, 13 Aug 2015 01:15:45 GMT

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

T Jake Luciani commented on CASSANDRA-10060:
--------------------------------------------

yeah there is a single batchlog for all MV updates

> Reuse TemporalRow when updating multiple MaterializedViews
> ----------------------------------------------------------
>
>                 Key: CASSANDRA-10060
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-10060
>             Project: Cassandra
>          Issue Type: Improvement
>            Reporter: T Jake Luciani
>            Assignee: T Jake Luciani
>             Fix For: 3.0.0 rc1
>
>
> 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)

Mime
View raw message