cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "C. Scott Andreas (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CASSANDRA-10307) Avoid always locking the partition key when a table has a materialized view
Date Sun, 18 Nov 2018 18:04:02 GMT

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

C. Scott Andreas updated CASSANDRA-10307:
-----------------------------------------
    Component/s: Materialized Views

> 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
>          Components: Materialized Views
>            Reporter: T Jake Luciani
>            Priority: Major
>              Labels: materializedviews
>             Fix For: 4.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
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org


Mime
View raw message