[
https://issues.apache.org/jira/browse/CASSANDRA-9054?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15399828#comment-15399828
]
Robert Stupp commented on CASSANDRA-9054:
-----------------------------------------
Alright - pushed a couple of commits to the branch to address the review
comments and also fix some things.
utests + dtests look good now. Latest dtest run has 0 errors an utest a couple
of timeouts (triggered another run).
Worked in all the review comments. Just removed the weird comments in Config +
DD. The intention of these comments was to hint contributors to be careful to
not introduce new "magic" class dependencies that startup "everything" by
accessing DD.
> 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)