[
https://issues.apache.org/jira/browse/SOLR-10272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15987353#comment-15987353
]
Jan Høydahl commented on SOLR-10272:
------------------------------------
bq. When Solr starts up, the datadriven configset is uploaded to ZK, called
"_default".
Are we sure we want to upload a new {{_default}} thingie? Default does not
really say anything, just like the old {{collection1}} default was not a great
idea. The bin/solr script uploads a config to a user-named config - or if no
name given - to a new config with the same name as the collection. Should not
the Collection API behaviour be something like that?
bq. Then in SOLR-10574 I think we can discuss modifying this config, perhaps
making a data-driven option toggle-able instead of fundamental to the config.
That could work. Perhaps write in CHANGES that the default is to be considered
experimental for the next few releases...
> 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: [email protected]
For additional commands, e-mail: [email protected]
