cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (JIRA)" <j...@apache.org>
Subject [jira] Commented: (CASSANDRA-1563) system_update_column_family() sets absent values to 0
Date Mon, 04 Oct 2010 21:52:33 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-1563?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12917786#action_12917786
] 

Jonathan Ellis commented on CASSANDRA-1563:
-------------------------------------------

When given a null value to an optional field it's very clear in my mind that the "right" thing
to do is to leave that field set to the current value.  It's much less work for the user to
manually override a field back to default if necessary, than to populate the entire KsDef/CfDef
w/ the current values to avoid stomping them.

If there are optional fields where null is a valid value, then we have a bug.  Do any such
exist?

> system_update_column_family() sets absent values to 0
> -----------------------------------------------------
>
>                 Key: CASSANDRA-1563
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-1563
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 0.7 beta 1
>            Reporter: Tyler L. Hobbs
>            Assignee: Jon Hermes
>         Attachments: reproduce.txt
>
>
> When system_update_keyspace() is supplied with a CfDef that does not have, for example,
min_compaction_threshold or gc_grace_seconds, it sets them to zero.  I would expect them to
be unchanged, instead.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message