[
https://issues.apache.org/jira/browse/SOLR-17006?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17777745#comment-17777745
]
ASF subversion and git services commented on SOLR-17006:
--------------------------------------------------------
Commit 0f5a8f929ee408eb5190bb7a4e8ff58560a273e9 in solr's branch
refs/heads/main from Vincent P
[ https://gitbox.apache.org/repos/asf?p=solr.git;h=0f5a8f929ee ]
SOLR-17006: Collections/AddReplica: Persist user-defined properties to
state.json (#1973)
User-defined properties are persisted to state.json so that any new replica
will use them. Adding a replica can also specify properties and they are saved
to state.json and override that of the collection.
---------
Co-authored-by: Vincent Primault <[email protected]>
> Persist user-defined core properties
> ------------------------------------
>
> Key: SOLR-17006
> URL: https://issues.apache.org/jira/browse/SOLR-17006
> Project: Solr
> Issue Type: Improvement
> Reporter: Vincent Primault
> Priority: Minor
> Time Spent: 2.5h
> Remaining Estimate: 0h
>
> CREATE collection and ADDREPLICA commands both accept core properties (as
> property.* parameters) that are then added to the core.properties file.
> However, those additional properties are not persisted anywhere in the
> cluster state.
> Consequently, cores that are added later to a collection (e.g., by adding a
> new replica) do not contain those properties, which seems inconsistent. I
> would like to be able to specify a core property when creating a collection,
> and not repeat myself when adding a new replica later on.
> *It might be a breaking change if people do not expect this behaviour though.*
> Related to SOLR-16305.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
