On 12/27/2017 7:06 AM, Alessandro Hoss wrote: > After reading this > <https://lucene.apache.org/solr/guide/7_0/major-changes-in-solr-7.html#new-default-configset> > docs, > I'm trying to achieve the following with version 7.2.0: > > - > When creating a new collection, if you *do not specify a configSet*, the > _default will be used. > - > > *If you use standalone mode, the instanceDir will be created > automatically, using the _defaultconfigSet as it’s basis.* > > But if I try to create a *core* in standalone mode without specifying a > configset, it searches for config files and throw this:
How are you doing the core create? If you're using the CoreAdmin API (either through the admin UI or using HTTP calls directly), then you cannot do it. CoreAdmin is *ancient* and is just a way to add an existing core directory to Solr. It has never copied configs, and if I had to guess, likely never will, unless a lot of users demand it. If you use "bin/solr create" or "bin\solr create" (depending on OS), then your expected behavior should be what you get in version 7 -- it should create a new core directory, copy the _default configset to a conf directory inside it, and then use an HTTP call to add the new core to Solr. > And if I specify the configSet parameter, it uses the configset folder > instead of copying the conf folder to the new instanceDir. That is exactly what the configset feature is designed to do. It emulates the behavior of SolrCloud in standalone mode, where the instanceDir does not have a conf directory. A central config directory is used. Shawn
