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-10307) Avoid always locking the partition key when a table has a materialized view
Date Fri, 11 Sep 2015 14:39:45 GMT

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

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

This would need to be some kind of data structure that tracks the clustering keys and ranges
in flight for a given partition key.  If it intersects with any existing ones then it will
require wait till the other request is finished 

> 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
>              Labels: materializedviews
>             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)

Mime
View raw message