[
https://issues.apache.org/jira/browse/CASSANDRA-3794?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13283528#comment-13283528
]
Sylvain Lebresne commented on CASSANDRA-3794:
---------------------------------------------
Two small nits while looking at v2 quickly:
* In fromSchemaNoColumns, the try catch is not useful.
* In ColumnFamilySerializer, when we serialize for an old version and can't
find an oldId, it'll probably be better to use a more user friendly message
like "Cannot send column family X to Y as it's version is pre-1.1.1. Please
update the whole cluster to 1.1.1 first".
But I think we agreed that it's safer to target this at 1.2 and acknowledge
that concurrent table creation will only be supported then, so this will need
rebase to trunk :)
> Avoid ID conflicts from concurrent schema changes
> -------------------------------------------------
>
> Key: CASSANDRA-3794
> URL: https://issues.apache.org/jira/browse/CASSANDRA-3794
> Project: Cassandra
> Issue Type: Improvement
> Components: Core
> Reporter: Pavel Yaskevich
> Assignee: Pavel Yaskevich
> Fix For: 1.1.1
>
> Attachments: CASSANDRA-3794-v2.patch, CASSANDRA-3794.patch
>
>
> Change ColumnFamily identifiers to be UUIDs instead of sequential Integers.
> Would be useful in the situation when nodes simultaneously trying to create
> ColumnFamilies.
--
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
