You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Abhishek Kumar Singh (JIRA)" <ji...@apache.org> on 2017/12/11 19:11:00 UTC
[jira] [Created] (SOLR-11744) ConfigSetAdminRequest.CREATE should
allow null in baseConfigSetName
Abhishek Kumar Singh created SOLR-11744:
-------------------------------------------
Summary: ConfigSetAdminRequest.CREATE should allow null in baseConfigSetName
Key: SOLR-11744
URL: https://issues.apache.org/jira/browse/SOLR-11744
Project: Solr
Issue Type: Wish
Security Level: Public (Default Security Level. Issues are Public)
Components: config-api, Tests
Reporter: Abhishek Kumar Singh
Priority: Minor
Currently,
[ConfigSetAdminRequest.Create|http://lucene.apache.org/solr/6_5_0/solr-solrj/org/apache/solr/client/solrj/request/ConfigSetAdminRequest.Create.html] gives an exception *_{color:red}no Base ConfigSet specified!{color}_* if [baseConfigSetName|http://lucene.apache.org/solr/6_5_0/solr-solrj/org/apache/solr/client/solrj/request/ConfigSetAdminRequest.Create.html#baseConfigSetName] is null.
However, a configSet can be created by passing the *__default_* as the {{baseConfigSetName}} which is a hack.
IMO *_baseConfigSetName_* should be optional, so that, instead of giving an exception, *_ConfigSetAdminRequest.Create_* lets the user create a *_configSet_* from the *_default config set_* i.e. *__default_* if the *_baseConfigSetName_* is not provided.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org