[ https://issues.apache.org/jira/browse/CASSANDRA-10060?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14698842#comment-14698842 ]
Carl Yeksigian commented on CASSANDRA-10060: -------------------------------------------- Overall, +1. {{TemporalRow.Type}} isn't really necessary - we always call {{setTombstonedExisting}} after we do the tombstone, so the extra state doesn't add more information, we could go back to the {{isNew}} flag instead. > 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)