You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Sylvain Lebresne (JIRA)" <ji...@apache.org> on 2011/03/04 11:31:36 UTC
[jira] Updated: (CASSANDRA-1559) make
{SuperColumn,ColumnFamily}.addColumn() correct in the face of concurrent
removals
[ https://issues.apache.org/jira/browse/CASSANDRA-1559?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sylvain Lebresne updated CASSANDRA-1559:
----------------------------------------
Attachment: 0001-Make-addColumn-deal-with-concurrent-deletion.patch
I took the liberty to rebase this to current 0.7 branch.
> make {SuperColumn,ColumnFamily}.addColumn() correct in the face of concurrent removals
> --------------------------------------------------------------------------------------
>
> Key: CASSANDRA-1559
> URL: https://issues.apache.org/jira/browse/CASSANDRA-1559
> Project: Cassandra
> Issue Type: Improvement
> Components: Core
> Affects Versions: 0.7 beta 1
> Reporter: Peter Schuller
> Priority: Trivial
> Fix For: 0.7.4
>
> Attachments: 0001-Make-addColumn-deal-with-concurrent-deletion.patch, trunk-1559.txt
>
>
> As reported on the mailing list, the particular lock-less spinning used during column addition is not correct for the case of concurrent removals. As also agreed, concurrent removals do not actually happen.
> Attaching a patch which, as jbellis suggests as an alternative to documenting the restriction on removals not being supported concurrently, makes addColumn() handle that case.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira