: I can't reproduce the problem you are seeing -- can you please provide
: more details..
Correction: i can reproduce this.
This was in fact some odd behavior in the 1.x and 3.x lines that has been
changed for 4.x in SOLR-1897.
If you had no <dataDir> in your solrconfig.xml, or if you had a *blank*
<dataDir></dataDir> then prior to 4.x the dataDir option specified when
CREATEing a core would override the default -- but if you had any real
path specified, then it would trump anything specified at runtime.
The "workarround" i believe (but i haven't tested exhaustively) for
3.4-3.6.1 is not to specify a hardcoded dataDir in your solrconig.xml, but
instead specify a property with a "default" value for the dataDir that can, and
then
use that property when issuing the CREATE command, ie...
<dataDir>${yourPropertyName:/some/default/path}</dataDir>
?action=CREATE&name=yourCoreName&instanceDir=yourCoreDir&property.yourPropertyName=/override/path
-Hoss
