[
https://issues.apache.org/jira/browse/CASSANDRA-1186?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12881182#action_12881182
]
Jonathan Ellis commented on CASSANDRA-1186:
-------------------------------------------
Thrift can absolutely handle this if the new field is marked optional (and
doesn't change the order of the old fields). I imagine something similar
applies to Avro, since this is very much a use case it is designed for.
> futureproof [KS|CF]MetaData
> ---------------------------
>
> Key: CASSANDRA-1186
> URL: https://issues.apache.org/jira/browse/CASSANDRA-1186
> Project: Cassandra
> Issue Type: Improvement
> Components: Core
> Affects Versions: 0.7
> Reporter: Jonathan Ellis
> Assignee: Gary Dusbabek
> Priority: Critical
> Fix For: 0.7
>
>
> KSMetaData/CFMetaData serialization is fragile. We need to be able to add
> fields easily without breaking when we read old-style serialized bytes.
> Avro and Thrift are designed to handle this. We should probably use one of
> those rather than re-inventing the wheel. If Avro is mature enough for this
> then let's use that, otherwise let's use Thrift.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
