: I wonder if what doesn't work is trying to set an explicit relative path
: there, instead of using the baked in default "data". If you set an explicit
: relative path, is it relative to the current core solr.home, or to the main
: solr.home?
it's realtive the current working dir of the process.
: Is _that_ a bug?
it's more an artifact of evolution -- it's just always worked that way,
and changing it now would be a pretty nasty break for existing users.
if people are interested in helping to fix this, my vote would be to see a
patch that let you include an optional 'rel' attribute on the data dir to
say what you wnat the path to be relative to...
<dataDir rel="solrHome">foo</dataDir>
<dataDir rel="instanceDir">foo</dataDir>
<dataDir rel="cwd">foo</dataDir> <!-- default, current behavior -->
typically people either use the default, or want a specific path outside
of the solr home altogether (ie: on a completley differnet partion) and
just use an absolute path, so it doesn't wind up being a big burden.
The biggest issue was the one that's already been mentioned: for a
while the main example solrconfig.xml was using...
<dataDir>${solr.data.dir:./data}</dataDir>
...instead of...
<dataDir>${solr.data.dir:}</dataDir>
...meaning that the dataDir defaulted to "./data" (relative the CWD)
instead of "" (which tells Solr to use it's own default in the
instanceDir) but this has been fixed for 3.x
-Hoss
