You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Yonik Seeley (JIRA)" <ji...@apache.org> on 2015/05/22 16:22:17 UTC
[jira] [Commented] (SOLR-5955) Add config templates to SolrCloud.
[ https://issues.apache.org/jira/browse/SOLR-5955?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14556204#comment-14556204 ]
Yonik Seeley commented on SOLR-5955:
------------------------------------
Perhaps more general functionality : the ability to easily make a copy of a configset and the ability to easily switch what configset is being used for a collection.
This covers a lot more usecases. Multiple collections share a configset but then you can make a new one based on the old one, switch only one collection over to it and try it out before migrating the others.
The fact that something is a template vs just a normal config set could be one of convention (i.e. any configset can be a template).
There could even be an implicit default template called something clever like "default_template" to cover Mark's original use case.
> 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: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org