[
https://issues.apache.org/jira/browse/CASSANDRA-1391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13190476#comment-13190476
]
Sylvain Lebresne commented on CASSANDRA-1391:
---------------------------------------------
bq. although would it be better to name ColumnFamilies using camel-case
Making them fully lowercase internally would make them case-insensitive without
any work using the current patch for CASSANDRA-3761. It's not really a big deal
in any case because 1) the patch for CASSANDRA-3761 is not yet committed so it
could change and 2) it won't be very hard to had some special casing for those
if we wish so. But if nobody has a preference, I would suggest calling them
'keyspaces' and 'columnfamilies' directly.
> Allow Concurrent Schema Migrations
> ----------------------------------
>
> Key: CASSANDRA-1391
> URL: https://issues.apache.org/jira/browse/CASSANDRA-1391
> Project: Cassandra
> Issue Type: Improvement
> Components: Core
> Affects Versions: 0.7.0
> Reporter: Stu Hood
> Assignee: Pavel Yaskevich
> Priority: Critical
> Fix For: 1.1
>
> Attachments: 0001-CASSANDRA-1391-main.patch,
> 0002-CASSANDRA-1391-fixes.patch, 1391-rebased.txt, CASSANDRA-1391.patch
>
>
> CASSANDRA-1292 fixed multiple migrations started from the same node to
> properly queue themselves, but it is still possible for migrations initiated
> on different nodes to conflict and leave the cluster in a bad state. Since
> the system_add/drop/rename methods are accessible directly from the client
> API, they should be completely safe for concurrent use.
> It should be possible to allow for most types of concurrent migrations by
> converting the UUID schema ID into a VersionVectorClock (as provided by
> CASSANDRA-580).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
