[
https://issues.apache.org/jira/browse/CASSANDRA-1186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stu Hood updated CASSANDRA-1186:
--------------------------------
Attachment: 0007-Separate-Definitions-from-Migrations.patch
0001
Renames config.Keyspace and config.ColumnFamily to match RawColumnDefinition.
0002
Creates an Avro protocol (with no methods) for internal serialization use. This
one will probably cause debate, but I'm fairly sure we want to separate
interface from internal. A better name than 'protocol' would be nice though.
0003
Separates OutputBuffer from DataOutputBuffer, in case someone doesn't need the
DataOutput interface.
0004
Adds the SerDeUtils class, which should be a sufficient replacement for all
ICompactSerializers (as more objects are converted to Avro serialization).
0005
Port the config metadata classes to Avro serialization.
0006
Use Avro serialization in the Definitions table and for the metadata portion of
Migrations.
0007
Remove duplication/improve encapsulation between DefsTable and Migrations
> 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: Stu Hood
> Priority: Critical
> Fix For: 0.7
>
> Attachments:
> 0001-Move-Yaml-related-classes-aside-to-reuse-names.patch,
> 0002-Extract-Avro-generation-and-begin-generating-an-inte.patch,
> 0003-Split-OutputBuffer-out-for-reuse.patch,
> 0004-Add-utility-functions-for-dealing-with-Avro-serializ.patch,
> 0005-Replace-serialization-code-in-KS-CF-CMetaData.patch,
> 0006-Port-Migrations-and-DefsTable-to-Avro.patch,
> 0007-Separate-Definitions-from-Migrations.patch
>
>
> 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.
