Are there any use cases for CREATE where the instance directory *doesn't* yet exist? I ask because I've noticed that Solr will create an instance directory for me sometimes with the CREATE command. In particular, if I run something like
http://solrhost/solr/admin/cores?action=CREATE&name=newcore&instanceDir=d:\dir_that_does_not_exist\&config=C:\dir_that_does_exist\solrconfig.xml&schema=C:\dir_that_does_exist\schema.xml then Solr will create d:\dir_that_does_not_exist and d:\dir_that_does_not_exist\data for me (but not d:\dir_that_does_not_exist\conf). Maybe this has to do with some particularly in my solrconfig.xml? (There I've commented out the dataDir element because I prefer the default behavior to what you get with "${solr.data.dir:./solr/data}".) 2009/11/23 Shalin Shekhar Mangar <shalinman...@gmail.com>: > The instance directory and the configuration files should exist before you > can create a core. The core CREATE command just creates a Solr core instance > in memory after reading the configuration from disk.
