[
https://issues.apache.org/jira/browse/SOLR-17875?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eric Pugh resolved SOLR-17875.
------------------------------
Fix Version/s: main (10.0)
Assignee: Eric Pugh
Resolution: Fixed
This is done. The rest of the system properties are just being done under
https://issues.apache.org/jira/browse/SOLR-17864.
> Rationalize bootstrap_conf, bootstrap_confdir, and -Dcollection.configName in
> start up scripts
> ----------------------------------------------------------------------------------------------
>
> Key: SOLR-17875
> URL: https://issues.apache.org/jira/browse/SOLR-17875
> Project: Solr
> Issue Type: Sub-task
> Affects Versions: main (10.0)
> Reporter: Eric Pugh
> Assignee: Eric Pugh
> Priority: Minor
> Labels: pull-request-available
> Fix For: main (10.0)
>
> Time Spent: 5h 10m
> Remaining Estimate: 0h
>
> During work on migrating system properties, and reviewing the
> [https://cwiki.apache.org/confluence/display/SOLR/System+property+naming+structure]
> spreadsheet, the use of bootstrap_conf, bootstrap_confdir, and
> collection.configName as system properties is in doubt...
>
> collection.configName is ONLY set as a sys prop IF you have bootstrap_conf in
> the solr start scripts. And guess what, it's never read ;-(. The property
> is used all over the code base in api calls and other places. What we are
> talking about eliminating is it being set as part of
> boostrap_conf/bootstrap_confdir.
>
> Need to see if maybe the Docker stuff used this?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org
For additional commands, e-mail: issues-h...@solr.apache.org
