cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eric Evans (JIRA)" <j...@apache.org>
Subject [jira] Commented: (CASSANDRA-2001) 0.7 migrations/schema serializations are incompatible with trunk
Date Tue, 18 Jan 2011 17:55:44 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-2001?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12983288#action_12983288
] 

Eric Evans commented on CASSANDRA-2001:
---------------------------------------

Just for posterity sake: CASSANDRA-926 moved  the remaining Avro records from o.a.c.avro elsewhere,
to packages that made it obvious which components were still using them (but obviously, created
a bug in the process).

+1 on this patchset though (with or without the o.a.c.db.migration.avro -> o.a.c.db.avro
move).

> 0.7 migrations/schema serializations are incompatible with trunk
> ----------------------------------------------------------------
>
>                 Key: CASSANDRA-2001
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-2001
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>            Reporter: Gary Dusbabek
>            Assignee: Gary Dusbabek
>            Priority: Minor
>             Fix For: 0.8
>
>         Attachments: v1-0001-use-the-writer-schema-and-not-the-current-schema-when-.txt,
v1-0002-get-rid-of-the-avro-db.migrations-classes-that-were-du.txt, v1-0003-fix-order-of-replicate_on_write-and-make-sure-it-s-not.txt
>
>
> Two problems:
> 1. inserting replicate_on_write into the middle of the CfDef members created a problem
with serialization.  
> 2. merging the genavro files created a strange namespacing problem.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message