cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sylvain Lebresne (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-3794) Avoid ID conflicts from concurrent schema changes
Date Mon, 21 May 2012 08:23:41 GMT


Sylvain Lebresne commented on CASSANDRA-3794:

Previous oppositions weren't mine but in any case I'm personally good going with #3 too (Pavel's
patch already includes the id<->uuid mapping, our only problem is the dropping of streaming
connection on version mismatch). This fix doesn't affect anything streamed, so it should be
fine to bump the messaging version but special case streaming so that it doesn't drop the
connection for streams coming from 1.1.0.
> Avoid ID conflicts from concurrent schema changes
> -------------------------------------------------
>                 Key: CASSANDRA-3794
>                 URL:
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>            Reporter: Pavel Yaskevich
>            Assignee: Pavel Yaskevich
>             Fix For: 1.1.1
>         Attachments: 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:!default.jspa
For more information on JIRA, see:


View raw message