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.