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/09/11 16:14:47 UTC

[jira] [Created] (CASSANDRA-10307) Avoid always locking the partition key when a table has a materialized view

T Jake Luciani created CASSANDRA-10307:
------------------------------------------

             Summary: Avoid always locking the partition key when a table has a materialized view
                 Key: CASSANDRA-10307
                 URL: https://issues.apache.org/jira/browse/CASSANDRA-10307
             Project: Cassandra
          Issue Type: Improvement
            Reporter: T Jake Luciani
             Fix For: 3.x


When a table has associated materialized views we must restrict other concurrent changes to the affected rows.  We currently lock the entire partition.  

The issue is many updates to the same partition on the base table is now serialized effectively.

We can't lock the primary key instead due to range tombstones cover a range of rows.

If we created (or perhaps reuse if already exists) a clustering range class we can lock at this level. 



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