[
https://issues.apache.org/jira/browse/CASSANDRA-840?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12843067#action_12843067
]
Gary Dusbabek commented on CASSANDRA-840:
-----------------------------------------
I had some more thoughts on this last night.
>I do think that Multilock is definitely overkill.
My idea was to lock a table during a definition mutation in order to prevent a
row mutation from happening in progress. I still think we need this. And I
think a per-table lock gives us more availability than a global table open lock.
I took a look at the code and since all row mutations go through
RowMutation.apply(), we're in good shape for this. I couldn't find any code
that hangs on to Table objects and calls Table.apply() at various times
(although nothing in the code prevents this).
>If it's not let's see if we can come up with a way to use Concurrent
>operations instead of trying to lock everyone.
This makes sense.
> Add the ability to add/remove/rename column families on a single node.
> ----------------------------------------------------------------------
>
> Key: CASSANDRA-840
> URL: https://issues.apache.org/jira/browse/CASSANDRA-840
> Project: Cassandra
> Issue Type: Sub-task
> Components: Core
> Reporter: Gary Dusbabek
> Assignee: Gary Dusbabek
> Priority: Minor
> Fix For: 0.7
>
> Attachments: v1-0001-store-cfid-map-in-CLH.txt,
> v1-0002-establish-ordering-of-cfids.txt,
> v1-0003-add-a-cf-on-a-single-node.txt,
> v1-0004-drop-a-cf-on-a-single-node.txt,
> v1-0005-rename-a-cf-on-a-single-node.txt,
> v1-0006-alternate-locking-approach.txt
>
>
> We need the ability to manipulate the KS/CF definitions structures in
> DatabaseDescriptor.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
