You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@cassandra.apache.org by "Blake Eggleston (JIRA)" <ji...@apache.org> on 2014/08/27 19:45:57 UTC

[jira] [Updated] (CASSANDRA-7840) Refactor static state & functions into static singletons

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

Blake Eggleston updated CASSANDRA-7840:
---------------------------------------

    Description: 
1st step of CASSANDRA-7837.

Things like DatabaseDescriptor.getPartitioner() should become DatabaseDescriptor.instance.getPartitioner(). In cases where there is a mix of instance state and static functionality (Keyspace & ColumnFamilyStore classes), the static portion should be split off into singleton factory classes.

  was:
1st step of CASSANDRA-7837.

Things lik DatabaseDescriptor.getPartitioner() should become DatabaseDescriptor.instance.getPartitioner(). In cases where there is a mix of instance state and static functionality (Keyspace & ColumnFamilyStore classes), the static portion should be split off into singleton factory classes.


> Refactor static state & functions into static singletons
> --------------------------------------------------------
>
>                 Key: CASSANDRA-7840
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-7840
>             Project: Cassandra
>          Issue Type: Improvement
>            Reporter: Blake Eggleston
>
> 1st step of CASSANDRA-7837.
> Things like DatabaseDescriptor.getPartitioner() should become DatabaseDescriptor.instance.getPartitioner(). In cases where there is a mix of instance state and static functionality (Keyspace & ColumnFamilyStore classes), the static portion should be split off into singleton factory classes.



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