You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Ekaterina Dimitrova (Jira)" <ji...@apache.org> on 2022/07/28 19:28:00 UTC
[jira] [Commented] (CASSANDRA-17783) Move {{Schema.FORCE_LOAD_KEYSPACES}} and {{Schema.FORCE_LOAD_KEYSPACES_PROP}} to {{CassandraRelevantProps}}
[ https://issues.apache.org/jira/browse/CASSANDRA-17783?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17572619#comment-17572619 ]
Ekaterina Dimitrova commented on CASSANDRA-17783:
-------------------------------------------------
[~jlewandowski] , [~ifesdjeen] do you mind to take a look into this one, please? It seems those were introduced in CASSANDRA-17044
> Move {{Schema.FORCE_LOAD_KEYSPACES}} and {{Schema.FORCE_LOAD_KEYSPACES_PROP}} to {{CassandraRelevantProps}}
> -----------------------------------------------------------------------------------------------------------
>
> Key: CASSANDRA-17783
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17783
> Project: Cassandra
> Issue Type: Improvement
> Reporter: Doug Rohrer
> Priority: Normal
>
> {{Schema.FORCE_LOAD_LOCAL_KEYSPACES_PROP}} and {{Schema.FORCE_LOAD_LOCAL_KEYSPACES}} should be moved to {{CassandraRelevantProps}} for two reasons.
> # Generally speaking, this is where these kinds of things live.
> # By having them in Schema, you can't actually use {{Schema.FORCE_LOAD_LOCAL_KEYSPACES_PROP}} without running all of the static initializers... and you want to use {{Schema.FORCE_LOAD_LOCAL_KEYSPACES_PROP}} to set the system property before the static initializer runs.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org