Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Mon, 11 Apr 2011 22:52:05 +0000 (UTC)
From: "Jonathan Ellis (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: 
 <923003032.50995.1302562325737.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Resolved] (CASSANDRA-1437) Improve default
 handling/validation for config.Metadata objects
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/CASSANDRA-1437?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jonathan Ellis resolved CASSANDRA-1437.
---------------------------------------

    Resolution: Duplicate

done in CASSANDRA-1906

> 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
>
> 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira