[
https://issues.apache.org/jira/browse/SOLR-5208?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13756119#comment-13756119
]
Mark Miller commented on SOLR-5208:
-----------------------------------
The CoreAdmin api already supports this with the property.* param naming scheme
on create calls - allowing this for the collections api is probably as simple
as propagating any property.* params from the collections api call to the
solrcore api subcalls. That seems like the best way to deal with this use case
- the core properties should be persisted already, so very simple to add I
think.
> Support for the setting of core.properties key/values at create-time on
> Collections API
> ---------------------------------------------------------------------------------------
>
> Key: SOLR-5208
> URL: https://issues.apache.org/jira/browse/SOLR-5208
> Project: Solr
> Issue Type: New Feature
> Components: SolrCloud
> Affects Versions: 4.4
> Reporter: Tim Vaillancourt
> Assignee: Erick Erickson
>
> As discussed on e-mail thread "Sharing SolrCloud collection configs
> w/overrides"
> (http://search-lucene.com/m/MUWXu1DIsqY1&subj=Sharing+SolrCloud+collection+configs+w+overrides),
> Erick brought up a neat solution using HTTP params at create-time for the
> Collection API.
> Essentially, this request is for a functionality that allows the setting of
> variables (core.properties) on Collections API CREATE command.
> Erick's idea:
> "Maybe it's as simple as allowing more params for creation like
> collection.coreName where each param of the form collection.blah=blort
> gets an entry in the properties file blah=blort?..."
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
