Return-Path: X-Original-To: apmail-cassandra-commits-archive@www.apache.org Delivered-To: apmail-cassandra-commits-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id C9FBF11F95 for ; Thu, 24 Jul 2014 11:59:38 +0000 (UTC) Received: (qmail 74188 invoked by uid 500); 24 Jul 2014 11:59:38 -0000 Delivered-To: apmail-cassandra-commits-archive@cassandra.apache.org Received: (qmail 74158 invoked by uid 500); 24 Jul 2014 11:59:38 -0000 Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cassandra.apache.org Delivered-To: mailing list commits@cassandra.apache.org Received: (qmail 74145 invoked by uid 99); 24 Jul 2014 11:59:38 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 24 Jul 2014 11:59:38 +0000 Date: Thu, 24 Jul 2014 11:59:38 +0000 (UTC) From: "Robert Stupp (JIRA)" To: commits@cassandra.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (CASSANDRA-7610) Remove static initializer in DatabaseDescriptor MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 Robert Stupp created CASSANDRA-7610: --------------------------------------- Summary: 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)