[jira] [Commented] (SOLR-10272) Use a default configset and make the configName parameter optional.

["Cassandra Targett (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/SOLR-10272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16023620#comment-16023620 ] 

Cassandra Targett commented on SOLR-10272:
------------------------------------------

I know this issue is about making the configName param optional, but what if we just pre-loaded all three examples at initial startup? It wouldn't remove the requirement that the configName param is specified, but it removes the need to pre-upload it. The CLI already requires you to choose one, but API users could use the Config API's LIST command to get a list of them, and UI users would see all of them in the UI to choose from.

Just throwing it out there - IMO it could accomplish a lot of the ease-of-use goals behind the idea for this issue, but doesn't require us to redo any examples or come up with odd names (like "_default") that aren't used anywhere else in the software.

> 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
>         Attachments: SOLR-10272.patch, SOLR-10272.patch.gz, SOLR-10272.patch.gz, SOLR-10272.patch.gz
>
>
> 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