[
https://issues.apache.org/jira/browse/SOLR-10272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16064780#comment-16064780
]
Ishan Chattopadhyaya edited comment on SOLR-10272 at 6/29/17 4:23 PM:
----------------------------------------------------------------------
-Just a note on errors like: "This is the _default configset, which is designed
to throw error upon collection creation."-
-Almost all tests either use the "conf1" configset (which is uploaded
initially) or explicitly upload a configset and use that. However, almost all
CREATE commands did not specify the configset name. After this change, if
configset name is not specified, the _default configset would be used. Hence,
*if you see this error*, it means you inadvertently used a _default configset
and you should modify your test to explicitly specify your configset name while
creating a collection (usually this is called "conf" or "conf1"). The _default
configset available to the test-framework is a bogus one that deliberately
throws that error so that no one inadvertently uses it and instead explicitly
specifies the required configset name.-
This is no longer the case after implementing the idea which Shalin proposed in
the subsequent comment.
was (Author: ichattopadhyaya):
Just a note on errors like: "This is the _default configset, which is designed
to throw error upon collection creation."
Almost all tests either use the "conf1" configset (which is uploaded initially)
or explicitly upload a configset and use that. However, almost all CREATE
commands did not specify the configset name. After this change, if configset
name is not specified, the _default configset would be used. Hence, *if you see
this error*, it means you inadvertently used a _default configset and you
should modify your test to explicitly specify your configset name while
creating a collection (usually this is called "conf" or "conf1"). The _default
configset available to the test-framework is a bogus one that deliberately
throws that error so that no one inadvertently uses it and instead explicitly
specifies the required configset name.
> 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
> 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 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.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
