You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Dave Brosius (Updated) (JIRA)" <ji...@apache.org> on 2012/02/26 01:29:49 UTC
[jira] [Updated] (CASSANDRA-3959) [patch] report bad meta data
field in cli instead of silently ignoring
[ https://issues.apache.org/jira/browse/CASSANDRA-3959?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dave Brosius updated CASSANDRA-3959:
------------------------------------
Attachment: better_cli_errors.diff
> [patch] report bad meta data field in cli instead of silently ignoring
> ----------------------------------------------------------------------
>
> Key: CASSANDRA-3959
> URL: https://issues.apache.org/jira/browse/CASSANDRA-3959
> Project: Cassandra
> Issue Type: Improvement
> Components: Tools
> Reporter: Dave Brosius
> Priority: Trivial
> Attachments: better_cli_errors.diff
>
>
> If cli is parsing an
> ^(ARRAY ^(HASH ^(PAIR .. ..) ^(PAIR .. ..)) ^(HASH ...))
> and a hash pair has a key that is unrecognized, it just ignores and continues.. better to report
> patch does this.
> for instance
> update column family cf with column_metadata = [{comparator_type:UTF8Type,column_name:idx,validation_class:IntegerType,index_type:0,index_name:idxname}];
> comparator_type is not processed, just ignored.
> (patch against trunk)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira