[
https://issues.apache.org/jira/browse/CASSANDRA-9054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Stupp updated CASSANDRA-9054:
------------------------------------
Status: Patch Available (was: In Progress)
Added a couple of unit tests for all offline tools.
These tests check the theads started by the tool invocation and the components
(say, {{Server}}, {{Schema}}, {{Keyspace}}, CLSM) initialized by a tool.
With this patch, referencing {{DatabaseDescriptor}} no longer implicitly starts
up everything.
Most of the patch is "noise" (e.g. to tell a unit test to startup or
refactorings to remove class dependencies). Details about that are in my long
comment above.
> Break DatabaseDescriptor up into multiple classes.
> --------------------------------------------------
>
> Key: CASSANDRA-9054
> URL: https://issues.apache.org/jira/browse/CASSANDRA-9054
> Project: Cassandra
> Issue Type: Improvement
> Reporter: Jeremiah Jordan
> Assignee: Robert Stupp
> Fix For: 3.x
>
>
> Right now to get at Config stuff you go through DatabaseDescriptor. But when
> you instantiate DatabaseDescriptor it actually opens system tables and such,
> which triggers commit log replays, and other things if the right flags aren't
> set ahead of time. This makes getting at config stuff from tools annoying,
> as you have to be very careful about instantiation orders.
> It would be nice if we could break DatabaseDescriptor up into multiple
> classes, so that getting at config stuff from tools wasn't such a pain.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
