You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@solr.apache.org by "Chris M. Hostetter (Jira)" <ji...@apache.org> on 2022/07/22 00:42:00 UTC

[jira] [Commented] (SOLR-16305) MODIFYCOLLECTION with 'property.*' changes can't change values used in config file variables (even though they can be set during collection CREATE)

    [ https://issues.apache.org/jira/browse/SOLR-16305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17569727#comment-17569727 ] 

Chris M. Hostetter commented on SOLR-16305:
-------------------------------------------

I don't have a good solution for this, but I ran into this today (and it caused me no end of confusion) so i wanted to make sure it was tracked.

IIUC the crux of the issue is that {{CREATE}} takes all these {{property.*}} collection "attributes" and passes them to he underlying CoreAdmin API when creating the cores – where they get baked into {{core.properties}} but there is no corrisponding CoreAdmin API for modifying the contents of the {{core.properties}} file, so there isn't really anything for {{MODIFYCOLLECTION}} to do with them to update the existing cores.

(I'm not really clear why/how the docs for  {{MODIFYCOLLECTION}}  include "other custom properties that use a {{property.}} prefix" in the list of supported attributes since I can't think of any way this would have ever worked?)

> 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
>            Priority: Major
>
> 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-unsubscribe@solr.apache.org
For additional commands, e-mail: issues-help@solr.apache.org