On 11/15/2017 2:28 AM, Amanda Shuman wrote:
1) so does this mean that on the back-end I should first create my new
core, e.g., core1 and then within that place a conf folder with all the
files? Same for the data folder? If so, is it fine to just use the existing
config files that I've previously worked on (i.e. the config for search
that I already modified)? I presume this won't be an issue.
2) does it matter if I create this core through the admin console or at
command line?
You can create your cores however you like. I actually create all my
cores completely by hand, including the core.properties file, and let
Solr discover them on startup. Mostly I just copy an existing core,
change core.properties to correct values, make any config changes I
need, and restart Solr.
If you want to use the admin UI (or the CoreAdmin API directly, which is
what the admin UI calls), then the instanceDir must have a conf
directory with all the config files you require for the core, and NOT
have a core.properties file. If you're adding a core that already has a
an index, then you would also include the data directory in the core's
instanceDir. If you want to relocate the data, you can add a dataDir
property to core.properties. If it has a relative path, it is relative
to the core.properties location.
The commandline creation works pretty well. The way it works is by
copying a configset (which may be in server/solr/configsets or in a
custom location) to the "conf" directory in the core, then calling the
CoreAdmin API to actually add the core to Solr (and create
core.properties so it'll get picked up on restart).
Thanks,
Shawn
