lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Smiley (JIRA)" <>
Subject [jira] [Commented] (SOLR-10272) Use a default configset and make the configName parameter optional.
Date Tue, 18 Apr 2017 16:19:41 GMT


David Smiley commented on SOLR-10272:

Thanks for doing this [~ichattopadhyaya]; overall your plan looks great.

But I'm concerned about the choice of the "data driven" configset being chosen as the default.
 The "data driven" feature is really only appropriate for fooling around; we shouldn't elevate
it's status as the new default.  I recall a conversation I had with [~noble.paul] and [~varunthacker]
in person in February and, I could be mistaken, but I think the 3 of us liked the idea of
a default configset that could be used that had the "add-unknown-fields-to-the-schema" URP
chain configured and available but not registered by default by /update.  For example, perhaps
a different /update/createSchema or something like that?  Heck; it could even be an URP chain
that deliberately has no RunUpdateProcessorFactory if it's job is purely to create the schema
for you.  I think [~hossman] had a similar idea discussed with us all at the last Lucene/Solr
Revolution.  I loved the idea!

> 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
> 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