Chris M. Hostetter created SOLR-16305:
-----------------------------------------
Summary: MODIFYCOLLECTION with 'property.*' changes can't change
values used in config file variables (even though they can be set during
collection CREATE)
Key: SOLR-16305
URL: https://issues.apache.org/jira/browse/SOLR-16305
Project: Solr
Issue Type: Bug
Security Level: Public (Default Security Level. Issues are Public)
Reporter: Chris M. Hostetter
Consider a configset with a {{solrconfig.xml}} that includes a snippet like
this...
{code:java}
<str name="param.check">${custom.prop:customDefVal}</str>
{code}
...this {{custom.prop}} can be set when doing a {{CREATE}} command for a
collection that uses this configset, using the {{property.*}} prefix as noted
in the reg-guide...
{quote}{{property.{_}name{_}={_}value{_}}}
|Optional|Default: none|
Set core property _name_ to {_}value{_}. See the section [Core
Discovery|https://solr.apache.org/guide/solr/latest/configuration-guide/core-discovery.html]
for details on supported properties and values.
{quote}
...BUT....
These values can *not* be changed by using the {{MODIFYCOLLECTION}} command, in
spite of the ref-guide indicating that it can be used to modify custom
{{property.*}} attributes...
{quote}The attributes that can be modified are:
* {{replicationFactor}}
* {{collection.configName}}
* {{readOnly}}
* other custom properties that use a {{property.}} prefix
See the [CREATE
action|https://solr.apache.org/guide/solr/latest/deployment-guide/collection-management.html#create]
section above for details on these attributes.
{quote}
--
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
