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-6) HashingStrategy does not default to RANDOM if the conf file is missing this entry
Date Wed, 08 Apr 2009 19:27:12 GMT

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

Jonathan Ellis commented on CASSANDRA-6:
----------------------------------------

attached patches that refuse to start up when things are broken.  (this means we don't need
the "default" value patch anymore.)

> HashingStrategy does not default to RANDOM if the conf file is missing this entry
> ---------------------------------------------------------------------------------
>
>                 Key: CASSANDRA-6
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-6
>             Project: Cassandra
>          Issue Type: Bug
>         Environment: all
>            Reporter: Sandeep Tata
>            Assignee: Jonathan Ellis
>            Priority: Minor
>         Attachments: 0001-don-t-manually-create-commitlog-directory-cassandra.patch,
0002-sanity-check-configuration-before-starting.patch, default_values_patch.txt
>
>   Original Estimate: 0.5h
>  Remaining Estimate: 0.5h
>
> When the conf file does not have a line for hashingstrategy, the value does not default
to RANDOM, instead it goes to null because of:
> DatabaseDescriptor.java:147
> hashingStrategy_ = xmlUtils.getNodeValue("/Storage/HashingStrategy");

-- 
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