cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Benedict (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (CASSANDRA-7610) Remove static initializer in DatabaseDescriptor
Date Thu, 24 Jul 2014 12:03:38 GMT

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

Benedict resolved CASSANDRA-7610.
---------------------------------

    Resolution: Duplicate

In general we prefer to transform a ticket if there is a simple change in scope. Simply update
the description with the updated goal given the new information. It makes it easier to track
the discussion in future, and reduces the number of extraneous tickets in the bug tracker

> Remove static initializer in DatabaseDescriptor
> -----------------------------------------------
>
>                 Key: CASSANDRA-7610
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-7610
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>            Reporter: Robert Stupp
>
> As discussed in CASSANDRA-7597 it's difficult to properly react on invalid configuration
values in a client tool that uses cassandra code (was an sstable loader).
> Reason is that the static initializer in DatabaseDescriptor calls System.exit in case
of configuration failures.
> Recommend to implement some "loadAndApplyConfig" method on DatabaseDescriptor and remove
the static initializer and let the calling code react accordingly (print error, exit VM).
> All direct and indirect uses of DatabaseDescriptor must be catched to solve this ticket
- so it's not a 2.x ticket.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message