Hi,
I have a maintenance use case where there are 2 collections defined, and I
need to do an remove core on one of the collections, and then be able to add
core that collection back in.
I can successfully remove the core with the 2ndary collection, but after I
add that core/collection back in
the
Shawn,
I agree the data dir concept doesn't make much sense in the context of
collections.
With the config I had setup the solr home was in a different file mount, so
I had to change my solr home
filemount location to get the data dir to locate where I wanted it once the
data dir option was removed
What I did to finally get this working was remove the
Catalina/localhost/solr.xml which was allowing the binary to be run from a
different location,
I made sure the solr.solr.home=/ebs-data/solr/conf was set to the file mount
I wanted and I then had
to remove the Dsolr.data.dir=/ebs-data/solr/data
Joel,
Yes we use that to force the data dir to be someplace other than solr.home.
Removing the data dir field just puts the data in solr home, which isn't
desirable.
solr home is specified in conf/Catalina/localhost/solr.xml
Is there any way to use the collections api with a data.dir set?
Th
