lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alan Woodward (JIRA)" <>
Subject [jira] [Commented] (SOLR-10272) Use a default configset and make the configName parameter optional.
Date Tue, 27 Jun 2017 09:09:00 GMT


Alan Woodward commented on SOLR-10272:

Hey Ishan, I think this has broken precommit?  ZkController is using the context class loader,
which is not permitted by forbidden-apis.

> Use a default configset and make the configName parameter optional.
> -------------------------------------------------------------------
>                 Key: SOLR-10272
>                 URL:
>             Project: Solr
>          Issue Type: Improvement
>      Security Level: Public(Default Security Level. Issues are Public) 
>            Reporter: Varun Thacker
>            Assignee: Ishan Chattopadhyaya
>            Priority: Blocker
>             Fix For: master (7.0)
>         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
> 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 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

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message