[
https://issues.apache.org/jira/browse/SOLR-17875?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18016272#comment-18016272
]
Eric Pugh commented on SOLR-17875:
----------------------------------
Okay, I think the new plan... There is what appears to be totally unused code
where if you had a "collection1", then we would load that using the bootstrap
command. It looks like it's left over from old demos and maybe how the
bin/post tool would be used.
I'll migrate these params to conforming names. I'll also look a bit more at
ConfigSetService.java and CreateCollectionCmd.java and make sure the use of
these system properties makes sense.
> 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
> Priority: Minor
>
> 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: [email protected]
For additional commands, e-mail: [email protected]
