[jira] [Updated] (CASSANDRA-17783) Move {{Schema.FORCE_LOAD_KEYSPACES}} and {{Schema.FORCE_LOAD_KEYSPACES_PROP}} to {{CassandraRelevantProps}}

2022-11-07 Thread Jacek Lewandowski (Jira)


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

Jacek Lewandowski updated CASSANDRA-17783:
--
  Fix Version/s: 4.1-beta2
 4.2
 (was: 4.x)
Source Control Link: 
https://github.com/apache/cassandra/commit/a805e3267572a86dc731df509f0540fc85e08b78
 Resolution: Fixed
 Status: Resolved  (was: Ready to Commit)

> 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
>  Components: Local/Startup and Shutdown
>Reporter: Doug Rohrer
>Assignee: Doug Rohrer
>Priority: Low
> Fix For: 4.1-beta2, 4.2
>
> Attachments: CASSANDRA-17783-rebased.patch
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> {{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-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org



[jira] [Updated] (CASSANDRA-17783) Move {{Schema.FORCE_LOAD_KEYSPACES}} and {{Schema.FORCE_LOAD_KEYSPACES_PROP}} to {{CassandraRelevantProps}}

2022-11-07 Thread Brandon Williams (Jira)


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

Brandon Williams updated CASSANDRA-17783:
-
Status: Ready to Commit  (was: Review In Progress)

> 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
>  Components: Local/Startup and Shutdown
>Reporter: Doug Rohrer
>Assignee: Doug Rohrer
>Priority: Low
> Fix For: 4.x
>
> Attachments: CASSANDRA-17783-rebased.patch
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> {{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-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org



[jira] [Updated] (CASSANDRA-17783) Move {{Schema.FORCE_LOAD_KEYSPACES}} and {{Schema.FORCE_LOAD_KEYSPACES_PROP}} to {{CassandraRelevantProps}}

2022-10-28 Thread Brandon Williams (Jira)


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

Brandon Williams updated CASSANDRA-17783:
-
Reviewers: Brandon Williams, Jacek Lewandowski  (was: Jacek Lewandowski)

> 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
>  Components: Local/Startup and Shutdown
>Reporter: Doug Rohrer
>Assignee: Doug Rohrer
>Priority: Low
> Fix For: 4.x
>
> Attachments: CASSANDRA-17783-rebased.patch
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> {{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-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org



[jira] [Updated] (CASSANDRA-17783) Move {{Schema.FORCE_LOAD_KEYSPACES}} and {{Schema.FORCE_LOAD_KEYSPACES_PROP}} to {{CassandraRelevantProps}}

2022-09-21 Thread Doug Rohrer (Jira)


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

Doug Rohrer updated CASSANDRA-17783:

Test and Documentation Plan: 
Tested in {{CQLSSTableWriterClientTest}} as it requires this prop to be set, 
which is done via the moved property in {{CQLSSTableWriter}}

 

See below for Trunk and 4.1 PRs for review and Circle CI runs.

 

 

  was:
 

Now rebased on Trunk from 8/23/2022 (a second time)

Tested in {{CQLSSTableWriterClientTest}} as it requires this prop to be set, 
which is done via the moved property in {{CQLSSTableWriter}}

 

 


> 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
>  Components: Local/Startup and Shutdown
>Reporter: Doug Rohrer
>Assignee: Doug Rohrer
>Priority: Low
> Fix For: 4.x
>
> Attachments: CASSANDRA-17783-rebased.patch
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> {{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-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org



[jira] [Updated] (CASSANDRA-17783) Move {{Schema.FORCE_LOAD_KEYSPACES}} and {{Schema.FORCE_LOAD_KEYSPACES_PROP}} to {{CassandraRelevantProps}}

2022-09-21 Thread Doug Rohrer (Jira)


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

Doug Rohrer updated CASSANDRA-17783:

Test and Documentation Plan: 
 

Now rebased on Trunk from 8/23/2022 (a second time)

Tested in {{CQLSSTableWriterClientTest}} as it requires this prop to be set, 
which is done via the moved property in {{CQLSSTableWriter}}

 

 

  was:
[^CASSANDRA-17783-rebased.patch]

Now rebased on Trunk from 8/23/2022 (a second time)

Tested in {{CQLSSTableWriterClientTest}} as it requires this prop to be set, 
which is done via the moved property in {{CQLSSTableWriter}}


> 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
>  Components: Local/Startup and Shutdown
>Reporter: Doug Rohrer
>Assignee: Doug Rohrer
>Priority: Low
> Fix For: 4.x
>
> Attachments: CASSANDRA-17783-rebased.patch
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> {{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-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org



[jira] [Updated] (CASSANDRA-17783) Move {{Schema.FORCE_LOAD_KEYSPACES}} and {{Schema.FORCE_LOAD_KEYSPACES_PROP}} to {{CassandraRelevantProps}}

2022-09-14 Thread Jacek Lewandowski (Jira)


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

Jacek Lewandowski updated CASSANDRA-17783:
--
Status: Review In Progress  (was: Patch Available)

> 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
>  Components: Local/Startup and Shutdown
>Reporter: Doug Rohrer
>Assignee: Doug Rohrer
>Priority: Low
> Fix For: 4.x
>
> Attachments: CASSANDRA-17783-rebased.patch
>
>
> {{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-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org



[jira] [Updated] (CASSANDRA-17783) Move {{Schema.FORCE_LOAD_KEYSPACES}} and {{Schema.FORCE_LOAD_KEYSPACES_PROP}} to {{CassandraRelevantProps}}

2022-09-14 Thread Jacek Lewandowski (Jira)


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

Jacek Lewandowski updated CASSANDRA-17783:
--
Reviewers: Jacek Lewandowski

> 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
>  Components: Local/Startup and Shutdown
>Reporter: Doug Rohrer
>Assignee: Doug Rohrer
>Priority: Low
> Fix For: 4.x
>
> Attachments: CASSANDRA-17783-rebased.patch
>
>
> {{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-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org



[jira] [Updated] (CASSANDRA-17783) Move {{Schema.FORCE_LOAD_KEYSPACES}} and {{Schema.FORCE_LOAD_KEYSPACES_PROP}} to {{CassandraRelevantProps}}

2022-08-23 Thread Doug Rohrer (Jira)


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

Doug Rohrer updated CASSANDRA-17783:

Test and Documentation Plan: 
 

Now rebased on Trunk from 8/23/2022

Tested in {{CQLSSTableWriterClientTest}} as it requires this prop to be set, 
which is done via the moved property in {{CQLSSTableWriter}}

  was:
[^CASSANDRA-17783-rebased.patch]

Now rebased on Trunk from 8/23/2022

Tested in {{CQLSSTableWriterClientTest}} as it requires this prop to be set, 
which is done via the moved property in {{CQLSSTableWriter}}


> 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
>  Components: Local/Startup and Shutdown
>Reporter: Doug Rohrer
>Priority: Low
> Fix For: 4.x
>
> Attachments: CASSANDRA-17783-rebased.patch
>
>
> {{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-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org



[jira] [Updated] (CASSANDRA-17783) Move {{Schema.FORCE_LOAD_KEYSPACES}} and {{Schema.FORCE_LOAD_KEYSPACES_PROP}} to {{CassandraRelevantProps}}

2022-08-23 Thread Doug Rohrer (Jira)


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

Doug Rohrer updated CASSANDRA-17783:

Test and Documentation Plan: 
[^CASSANDRA-17783-rebased.patch]

Now rebased on Trunk from 8/23/2022 (a second time)

Tested in {{CQLSSTableWriterClientTest}} as it requires this prop to be set, 
which is done via the moved property in {{CQLSSTableWriter}}

  was:
 

Now rebased on Trunk from 8/23/2022

Tested in {{CQLSSTableWriterClientTest}} as it requires this prop to be set, 
which is done via the moved property in {{CQLSSTableWriter}}


> 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
>  Components: Local/Startup and Shutdown
>Reporter: Doug Rohrer
>Priority: Low
> Fix For: 4.x
>
> Attachments: CASSANDRA-17783-rebased.patch
>
>
> {{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-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org



[jira] [Updated] (CASSANDRA-17783) Move {{Schema.FORCE_LOAD_KEYSPACES}} and {{Schema.FORCE_LOAD_KEYSPACES_PROP}} to {{CassandraRelevantProps}}

2022-08-23 Thread Doug Rohrer (Jira)


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

Doug Rohrer updated CASSANDRA-17783:

Attachment: CASSANDRA-17783-rebased.patch

> 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
>  Components: Local/Startup and Shutdown
>Reporter: Doug Rohrer
>Priority: Low
> Fix For: 4.x
>
> Attachments: CASSANDRA-17783-rebased.patch
>
>
> {{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-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org



[jira] [Updated] (CASSANDRA-17783) Move {{Schema.FORCE_LOAD_KEYSPACES}} and {{Schema.FORCE_LOAD_KEYSPACES_PROP}} to {{CassandraRelevantProps}}

2022-08-23 Thread Doug Rohrer (Jira)


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

Doug Rohrer updated CASSANDRA-17783:

Attachment: (was: CASSANDRA-17783.patch)

> 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
>  Components: Local/Startup and Shutdown
>Reporter: Doug Rohrer
>Priority: Low
> Fix For: 4.x
>
> Attachments: CASSANDRA-17783-rebased.patch
>
>
> {{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-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org



[jira] [Updated] (CASSANDRA-17783) Move {{Schema.FORCE_LOAD_KEYSPACES}} and {{Schema.FORCE_LOAD_KEYSPACES_PROP}} to {{CassandraRelevantProps}}

2022-08-23 Thread Doug Rohrer (Jira)


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

Doug Rohrer updated CASSANDRA-17783:

Attachment: (was: CASSANDRA-17783-rebased.patch)

> 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
>  Components: Local/Startup and Shutdown
>Reporter: Doug Rohrer
>Priority: Low
> Fix For: 4.x
>
> Attachments: CASSANDRA-17783-rebased.patch
>
>
> {{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-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org



[jira] [Updated] (CASSANDRA-17783) Move {{Schema.FORCE_LOAD_KEYSPACES}} and {{Schema.FORCE_LOAD_KEYSPACES_PROP}} to {{CassandraRelevantProps}}

2022-08-23 Thread Doug Rohrer (Jira)


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

Doug Rohrer updated CASSANDRA-17783:

Test and Documentation Plan: 
[^CASSANDRA-17783-rebased.patch]

Now rebased on Trunk from 8/23/2022

Tested in {{CQLSSTableWriterClientTest}} as it requires this prop to be set, 
which is done via the moved property in {{CQLSSTableWriter}}

  was:
[^CASSANDRA-17783.patch]

(NOTE: Updated - missed a file in the first upload)

Tested in {{CQLSSTableWriterClientTest}} as it requires this prop to be set, 
which is done via the moved property in {{CQLSSTableWriter}}


> 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
>  Components: Local/Startup and Shutdown
>Reporter: Doug Rohrer
>Priority: Low
> Fix For: 4.x
>
> Attachments: CASSANDRA-17783-rebased.patch, CASSANDRA-17783.patch
>
>
> {{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-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org



[jira] [Updated] (CASSANDRA-17783) Move {{Schema.FORCE_LOAD_KEYSPACES}} and {{Schema.FORCE_LOAD_KEYSPACES_PROP}} to {{CassandraRelevantProps}}

2022-08-23 Thread Doug Rohrer (Jira)


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

Doug Rohrer updated CASSANDRA-17783:

Attachment: CASSANDRA-17783-rebased.patch

> 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
>  Components: Local/Startup and Shutdown
>Reporter: Doug Rohrer
>Priority: Low
> Fix For: 4.x
>
> Attachments: CASSANDRA-17783-rebased.patch, CASSANDRA-17783.patch
>
>
> {{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-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org



[jira] [Updated] (CASSANDRA-17783) Move {{Schema.FORCE_LOAD_KEYSPACES}} and {{Schema.FORCE_LOAD_KEYSPACES_PROP}} to {{CassandraRelevantProps}}

2022-08-23 Thread Brandon Williams (Jira)


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

Brandon Williams updated CASSANDRA-17783:
-
Fix Version/s: 4.x

> 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
>  Components: Local/Startup and Shutdown
>Reporter: Doug Rohrer
>Priority: Low
> Fix For: 4.x
>
> Attachments: CASSANDRA-17783.patch
>
>
> {{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-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org



[jira] [Updated] (CASSANDRA-17783) Move {{Schema.FORCE_LOAD_KEYSPACES}} and {{Schema.FORCE_LOAD_KEYSPACES_PROP}} to {{CassandraRelevantProps}}

2022-08-23 Thread Brandon Williams (Jira)


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

Brandon Williams updated CASSANDRA-17783:
-
Status: Patch Available  (was: Open)

> 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
>  Components: Local/Startup and Shutdown
>Reporter: Doug Rohrer
>Priority: Low
> Fix For: 4.x
>
> Attachments: CASSANDRA-17783.patch
>
>
> {{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-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org



[jira] [Updated] (CASSANDRA-17783) Move {{Schema.FORCE_LOAD_KEYSPACES}} and {{Schema.FORCE_LOAD_KEYSPACES_PROP}} to {{CassandraRelevantProps}}

2022-08-01 Thread Doug Rohrer (Jira)


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

Doug Rohrer updated CASSANDRA-17783:

Test and Documentation Plan: 
[^CASSANDRA-17783.patch]

(NOTE: Updated - missed a file in the first upload)

Tested in {{CQLSSTableWriterClientTest}} as it requires this prop to be set, 
which is done via the moved property in {{CQLSSTableWriter}}

  was:
 

(NOTE: Updated - missed a file in the first upload)

Tested in {{CQLSSTableWriterClientTest}} as it requires this prop to be set, 
which is done via the moved property in {{CQLSSTableWriter}}


> 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
>  Components: Local/Startup and Shutdown
>Reporter: Doug Rohrer
>Priority: Low
> Attachments: CASSANDRA-17783.patch
>
>
> {{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-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org



[jira] [Updated] (CASSANDRA-17783) Move {{Schema.FORCE_LOAD_KEYSPACES}} and {{Schema.FORCE_LOAD_KEYSPACES_PROP}} to {{CassandraRelevantProps}}

2022-08-01 Thread Doug Rohrer (Jira)


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

Doug Rohrer updated CASSANDRA-17783:

Attachment: CASSANDRA-17783.patch

> 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
>  Components: Local/Startup and Shutdown
>Reporter: Doug Rohrer
>Priority: Low
> Attachments: CASSANDRA-17783.patch
>
>
> {{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-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org



[jira] [Updated] (CASSANDRA-17783) Move {{Schema.FORCE_LOAD_KEYSPACES}} and {{Schema.FORCE_LOAD_KEYSPACES_PROP}} to {{CassandraRelevantProps}}

2022-08-01 Thread Doug Rohrer (Jira)


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

Doug Rohrer updated CASSANDRA-17783:

Attachment: (was: CASSANDRA-17783.patch)

> 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
>  Components: Local/Startup and Shutdown
>Reporter: Doug Rohrer
>Priority: Low
> Attachments: CASSANDRA-17783.patch
>
>
> {{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-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org



[jira] [Updated] (CASSANDRA-17783) Move {{Schema.FORCE_LOAD_KEYSPACES}} and {{Schema.FORCE_LOAD_KEYSPACES_PROP}} to {{CassandraRelevantProps}}

2022-08-01 Thread Doug Rohrer (Jira)


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

Doug Rohrer updated CASSANDRA-17783:

Attachment: (was: CASSANDRA-17783-1.patch)

> 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
>  Components: Local/Startup and Shutdown
>Reporter: Doug Rohrer
>Priority: Low
> Attachments: CASSANDRA-17783.patch
>
>
> {{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-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org



[jira] [Updated] (CASSANDRA-17783) Move {{Schema.FORCE_LOAD_KEYSPACES}} and {{Schema.FORCE_LOAD_KEYSPACES_PROP}} to {{CassandraRelevantProps}}

2022-08-01 Thread Doug Rohrer (Jira)


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

Doug Rohrer updated CASSANDRA-17783:

Attachment: (was: CASSANDRA-17783-3.patch)

> 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
>  Components: Local/Startup and Shutdown
>Reporter: Doug Rohrer
>Priority: Low
> Attachments: CASSANDRA-17783.patch
>
>
> {{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-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org



[jira] [Updated] (CASSANDRA-17783) Move {{Schema.FORCE_LOAD_KEYSPACES}} and {{Schema.FORCE_LOAD_KEYSPACES_PROP}} to {{CassandraRelevantProps}}

2022-08-01 Thread Doug Rohrer (Jira)


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

Doug Rohrer updated CASSANDRA-17783:

Attachment: (was: CASSANDRA-17783.patch)

> 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
>  Components: Local/Startup and Shutdown
>Reporter: Doug Rohrer
>Priority: Low
> Attachments: CASSANDRA-17783.patch
>
>
> {{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-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org



[jira] [Updated] (CASSANDRA-17783) Move {{Schema.FORCE_LOAD_KEYSPACES}} and {{Schema.FORCE_LOAD_KEYSPACES_PROP}} to {{CassandraRelevantProps}}

2022-08-01 Thread Doug Rohrer (Jira)


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

Doug Rohrer updated CASSANDRA-17783:

Attachment: (was: CASSANDRA-17783-2.patch)

> 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
>  Components: Local/Startup and Shutdown
>Reporter: Doug Rohrer
>Priority: Low
> Attachments: CASSANDRA-17783.patch
>
>
> {{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-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org



[jira] [Updated] (CASSANDRA-17783) Move {{Schema.FORCE_LOAD_KEYSPACES}} and {{Schema.FORCE_LOAD_KEYSPACES_PROP}} to {{CassandraRelevantProps}}

2022-08-01 Thread Doug Rohrer (Jira)


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

Doug Rohrer updated CASSANDRA-17783:

Attachment: CASSANDRA-17783.patch

> 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
>  Components: Local/Startup and Shutdown
>Reporter: Doug Rohrer
>Priority: Low
> Attachments: CASSANDRA-17783.patch
>
>
> {{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-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org



[jira] [Updated] (CASSANDRA-17783) Move {{Schema.FORCE_LOAD_KEYSPACES}} and {{Schema.FORCE_LOAD_KEYSPACES_PROP}} to {{CassandraRelevantProps}}

2022-08-01 Thread Doug Rohrer (Jira)


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

Doug Rohrer updated CASSANDRA-17783:

Test and Documentation Plan: 
 

(NOTE: Updated - missed a file in the first upload)

Tested in {{CQLSSTableWriterClientTest}} as it requires this prop to be set, 
which is done via the moved property in {{CQLSSTableWriter}}

  was:
[^CASSANDRA-17783.patch]

(NOTE: Updated - missed a file in the first upload)

Tested in {{CQLSSTableWriterClientTest}} as it requires this prop to be set, 
which is done via the moved property in {{CQLSSTableWriter}}


> 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
>  Components: Local/Startup and Shutdown
>Reporter: Doug Rohrer
>Priority: Low
> Attachments: CASSANDRA-17783.patch
>
>
> {{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-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org



[jira] [Updated] (CASSANDRA-17783) Move {{Schema.FORCE_LOAD_KEYSPACES}} and {{Schema.FORCE_LOAD_KEYSPACES_PROP}} to {{CassandraRelevantProps}}

2022-08-01 Thread Doug Rohrer (Jira)


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

Doug Rohrer updated CASSANDRA-17783:

Attachment: CASSANDRA-17783-3.patch

> 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
>  Components: Local/Startup and Shutdown
>Reporter: Doug Rohrer
>Priority: Low
> Attachments: CASSANDRA-17783.patch
>
>
> {{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-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org



[jira] [Updated] (CASSANDRA-17783) Move {{Schema.FORCE_LOAD_KEYSPACES}} and {{Schema.FORCE_LOAD_KEYSPACES_PROP}} to {{CassandraRelevantProps}}

2022-08-01 Thread Doug Rohrer (Jira)


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

Doug Rohrer updated CASSANDRA-17783:

Status: Open  (was: Patch Available)

> 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
>  Components: Local/Startup and Shutdown
>Reporter: Doug Rohrer
>Priority: Low
> Attachments: CASSANDRA-17783-1.patch, CASSANDRA-17783-2.patch, 
> CASSANDRA-17783.patch
>
>
> {{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-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org



[jira] [Updated] (CASSANDRA-17783) Move {{Schema.FORCE_LOAD_KEYSPACES}} and {{Schema.FORCE_LOAD_KEYSPACES_PROP}} to {{CassandraRelevantProps}}

2022-08-01 Thread Doug Rohrer (Jira)


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

Doug Rohrer updated CASSANDRA-17783:

Test and Documentation Plan: 
[^CASSANDRA-17783.patch]

(NOTE: Updated - missed a file in the first upload)

Tested in {{CQLSSTableWriterClientTest}} as it requires this prop to be set, 
which is done via the moved property in {{CQLSSTableWriter}}

  was:
[^CASSANDRA-17783.patch] (NOTE: Updated - missed a file in the first upload)

Tested in {{CQLSSTableWriterClientTest}} as it requires this prop to be set, 
which is done via the moved property in {{CQLSSTableWriter}}


> 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
>  Components: Local/Startup and Shutdown
>Reporter: Doug Rohrer
>Priority: Low
> Attachments: CASSANDRA-17783-1.patch, CASSANDRA-17783-2.patch, 
> CASSANDRA-17783.patch
>
>
> {{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-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org



[jira] [Updated] (CASSANDRA-17783) Move {{Schema.FORCE_LOAD_KEYSPACES}} and {{Schema.FORCE_LOAD_KEYSPACES_PROP}} to {{CassandraRelevantProps}}

2022-08-01 Thread Doug Rohrer (Jira)


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

Doug Rohrer updated CASSANDRA-17783:

Attachment: CASSANDRA-17783-2.patch

> 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
>  Components: Local/Startup and Shutdown
>Reporter: Doug Rohrer
>Priority: Low
> Attachments: CASSANDRA-17783-1.patch, CASSANDRA-17783-2.patch, 
> CASSANDRA-17783.patch
>
>
> {{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-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org



[jira] [Updated] (CASSANDRA-17783) Move {{Schema.FORCE_LOAD_KEYSPACES}} and {{Schema.FORCE_LOAD_KEYSPACES_PROP}} to {{CassandraRelevantProps}}

2022-08-01 Thread Doug Rohrer (Jira)


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

Doug Rohrer updated CASSANDRA-17783:

Attachment: CASSANDRA-17783-1.patch

> 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
>  Components: Local/Startup and Shutdown
>Reporter: Doug Rohrer
>Priority: Low
> Attachments: CASSANDRA-17783-1.patch, CASSANDRA-17783.patch
>
>
> {{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-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org



[jira] [Updated] (CASSANDRA-17783) Move {{Schema.FORCE_LOAD_KEYSPACES}} and {{Schema.FORCE_LOAD_KEYSPACES_PROP}} to {{CassandraRelevantProps}}

2022-08-01 Thread Doug Rohrer (Jira)


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

Doug Rohrer updated CASSANDRA-17783:

Test and Documentation Plan: 
[^CASSANDRA-17783.patch] (NOTE: Updated - missed a file in the first upload)

Tested in {{CQLSSTableWriterClientTest}} as it requires this prop to be set, 
which is done via the moved property in {{CQLSSTableWriter}}

  was:
[^CASSANDRA-17783.patch]

 

Tested in {{CQLSSTableWriterClientTest}} as it requires this prop to be set, 
which is done via the moved property in {{CQLSSTableWriter}}


> 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
>  Components: Local/Startup and Shutdown
>Reporter: Doug Rohrer
>Priority: Low
> Attachments: CASSANDRA-17783-1.patch, CASSANDRA-17783.patch
>
>
> {{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-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org



[jira] [Updated] (CASSANDRA-17783) Move {{Schema.FORCE_LOAD_KEYSPACES}} and {{Schema.FORCE_LOAD_KEYSPACES_PROP}} to {{CassandraRelevantProps}}

2022-08-01 Thread Doug Rohrer (Jira)


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

Doug Rohrer updated CASSANDRA-17783:

Test and Documentation Plan: 
[^CASSANDRA-17783.patch]

 

Tested in {{CQLSSTableWriterClientTest}} as it requires this prop to be set, 
which is done via the moved property in {{CQLSSTableWriter}}

  was:Tested in {{CQLSSTableWriterClientTest}} as it requires this prop to be 
set, which is done via the moved property in {{CQLSSTableWriter}}


> 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
>  Components: Local/Startup and Shutdown
>Reporter: Doug Rohrer
>Priority: Low
> Attachments: CASSANDRA-17783.patch
>
>
> {{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-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org



[jira] [Updated] (CASSANDRA-17783) Move {{Schema.FORCE_LOAD_KEYSPACES}} and {{Schema.FORCE_LOAD_KEYSPACES_PROP}} to {{CassandraRelevantProps}}

2022-08-01 Thread Doug Rohrer (Jira)


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

Doug Rohrer updated CASSANDRA-17783:

Attachment: CASSANDRA-17783.patch

> 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
>  Components: Local/Startup and Shutdown
>Reporter: Doug Rohrer
>Priority: Low
> Attachments: CASSANDRA-17783.patch
>
>
> {{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-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org



[jira] [Updated] (CASSANDRA-17783) Move {{Schema.FORCE_LOAD_KEYSPACES}} and {{Schema.FORCE_LOAD_KEYSPACES_PROP}} to {{CassandraRelevantProps}}

2022-08-01 Thread Doug Rohrer (Jira)


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

Doug Rohrer updated CASSANDRA-17783:

Authors: Doug Rohrer
Test and Documentation Plan: Tested in {{CQLSSTableWriterClientTest}} as it 
requires this prop to be set, which is done via the moved property in 
{{CQLSSTableWriter}}
 Status: Patch Available  (was: Open)

> 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
>  Components: Local/Startup and Shutdown
>Reporter: Doug Rohrer
>Priority: Low
> Attachments: CASSANDRA-17783.patch
>
>
> {{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-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org



[jira] [Updated] (CASSANDRA-17783) Move {{Schema.FORCE_LOAD_KEYSPACES}} and {{Schema.FORCE_LOAD_KEYSPACES_PROP}} to {{CassandraRelevantProps}}

2022-08-01 Thread Doug Rohrer (Jira)


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

Doug Rohrer updated CASSANDRA-17783:

Change Category: Operability
 Complexity: Low Hanging Fruit
Component/s: Local/Startup and Shutdown
   Priority: Low  (was: Normal)
 Status: Open  (was: Triage Needed)

> 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
>  Components: Local/Startup and Shutdown
>Reporter: Doug Rohrer
>Priority: Low
>
> {{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-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org