Improve default handling/validation for config.Metadata objects
---------------------------------------------------------------
Key: CASSANDRA-1437
URL: https://issues.apache.org/jira/browse/CASSANDRA-1437
Project: Cassandra
Issue Type: Improvement
Components: Core
Reporter: Stu Hood
Priority: Minor
Fix For: 0.7.0
Post CASSANDRA-1436, we'll be back to single Avro objects to describe schemas
for client and internal use: it would be a good opportunity to improve our
handling of defaults and our validation of config.*Metadata objects.
Right now, we have multiple ways to convert a CfDef to a CFMetaData object (for
example), due to the differences between the defaults that should be chosen for
a _new_ column family (when we receive the CfDef from a client), versus an
_existing_ column family after a new setting has been added (deserializing a
CfDef from disk). Finding a unified way to handle these two (potentially
different) default values would be excellent.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
