You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Ishan Chattopadhyaya (JIRA)" <ji...@apache.org> on 2017/04/25 15:56:04 UTC
[jira] [Assigned] (SOLR-10272) Use a default configset and make the
configName parameter optional.
[ https://issues.apache.org/jira/browse/SOLR-10272?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ishan Chattopadhyaya reassigned SOLR-10272:
-------------------------------------------
Assignee: Ishan Chattopadhyaya
> Use a default configset and make the configName parameter optional.
> -------------------------------------------------------------------
>
> Key: SOLR-10272
> URL: https://issues.apache.org/jira/browse/SOLR-10272
> Project: Solr
> Issue Type: Improvement
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: Varun Thacker
> Assignee: Ishan Chattopadhyaya
>
> This Jira's motivation is to improve the creating a collection experience better for users.
> To create a collection we need to specify a configName that needs to be present in ZK. When a new user is starting Solr why should he worry about having to know about configsets before he can can create a collection.
> When you create a collection using "bin/solr create" the script uploads a configset and references it. This is great. We should extend this idea to API users as well.
> So here is the rough outline of what I think we can do here:
> 1. When you start solr , the bin script checks to see if "/configs/_baseConfigSet" znode is present . If not it uploads the "basic_configs".
> We can discuss if its the "basic_configs" or something other default config set.
> Also we can discuss the name for "/_baseConfigSet". Moving on though
> 2. When a user creates a collection from the API {{admin/collections?action=CREATE&name=gettingstarted}} here is what we do :
> Use https://cwiki.apache.org/confluence/display/solr/ConfigSets+API to copy over the default config set to a configset with the name of the collection specified.
> collection.configName can truly be an optional parameter. If its specified we don't need to do this step.
> 3. Have the bin scripts use this and remove the logic built in there to do the same thing.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org