[
https://issues.apache.org/jira/browse/SOLR-5208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Erick Erickson updated SOLR-5208:
---------------------------------
Attachment: SOLR-5208.patch
Man, I simply cannot make a test even start to work for this, and I'm past my
point of being willing to spend more time on it. Every time I try to add
property.key=value to the parameters, the persisted core.properties files do
not have anything there. And the code never goes through the usual persist
logic.
But outside the test environment, I've manually tested both create and split
and they work fine. So I'm going to commit this after I run through the
precommit and test process and leave it to someone more ambitious to untangle
the whole test bits.
> 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
> Attachments: SOLR-5208.patch, SOLR-5208.patch
>
>
> 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 was sent by Atlassian JIRA
(v6.1#6144)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
