[
https://issues.apache.org/jira/browse/SOLR-10272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15986661#comment-15986661
]
David Smiley commented on SOLR-10272:
-------------------------------------
The default at the CLI doesn't matter much to me because there are other
options at the CLI -- particularly "basic_configs". That isn't the case for
this feature -- a baked in SolrCloud default. So the default choice is way
more important here.
bq. Do you think we should decide upon the best choice for the default
configset first, before making whatever is the default be used by the
Collections API?
Unless the data-driven (auto schema modifications) can be easily disabled, then
yes.
If at this stage (this issue) we simply want to pick an existing config and not
make changes to any particular config, then I think the only suitable choice is
"basic_configs".
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_.
AFAIK that wouldn't involve new code; just some configuration in such a way
that users can toggle easily -- perhaps by setting {{update.chain}} with the
request parameters API:
https://cwiki.apache.org/confluence/display/solr/Request+Parameters+API
> 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]
