[
https://issues.apache.org/jira/browse/SOLR-5955?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14556395#comment-14556395
]
Anshum Gupta commented on SOLR-5955:
------------------------------------
It sounds like what I suggested but with the ability to dynamically switch a
config-set for a collection. That might get tricky unless you're only talking
about allowing a one time move from a shared config-set to a collection
specific config-set. e.g.
# collection1 uses conf1 (shared config-set)
# you want collection1 to have it's own copy of conf1, so you make the API
call, which copies the config to another location
{{(/collections/collection1/config/... )}} ? and then links it there.
# Going forward, you could edit this config using the API without worrying
about the impact on other collections.
It would be tricky to have an API that allows collection1 to be linked to a new
config called, conf2, and then in a while switch it to say, conf3, which may or
may-not be even compatible.
> Add config templates to SolrCloud.
> ----------------------------------
>
> Key: SOLR-5955
> URL: https://issues.apache.org/jira/browse/SOLR-5955
> Project: Solr
> Issue Type: New Feature
> Reporter: Mark Miller
> Attachments: SOLR-5955.patch
>
>
> You should be able to upload config sets to a templates location and then
> specify a template as your starting config when creating new collections via
> REST API. We can have a default template that we ship with.
> This will let you create collections from scratch via REST API, and then you
> can use things like the schema REST API to customize the template config to
> your needs.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
