: 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
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?
Let's try it to see Yep, THAT's what doesn't work, an
Meanwhile, I'm having trouble getting the expected behavior at all. I'll
try to give the right details (without overwhelming with too many), if
anyone can see what's going on.
Solr 1.4.1. Multi-core. 'Main' solr home with solr.xml at
/opt/solr/solr_indexer/solr.xml
The solr.xml includes actu
Yes - I commented out the element in solrconfig.xml and then
got the expected behavior: the core used a data subdirectory in the core
subdirectory.
It seems like the problem arises from using the solrconfig.xml that's
distributed as example/solr/conf/solrconfig.xml
The solrconfig.xml's in
HI Jonathan:
Did you try :
This should create the indexes under some_core/data or you can make
datadir relative to some_core dir.
Regards,
- NN
http://solr-ra.tgels.com
http://rankingalgorithm.tgels.com
On 3/1/2011 7:21 AM, Jonathan Rochkind wrote:
I did try that, yes. I tried that fi
:
: ${solr.data.dir:./solr/data}
that directive says "use the solr.data.dir system property to pick a path,
if it is not set, use "./solr/data" (realtive the CWD)
if you want it to use the default, then you need to eliminate it
completley, or you need to change it to the empty string...
${
This definitely matches my own experience, and I've heard it from
others. I haven't heard of anyone who HAS gotten it to work like that.
But apparently there's a distributed multi-core example which claims to
work like it doesn't for us.
One of us has to try the Solr distro multi-core example
I tried this in my 1.4.0 installation (commenting out what had been
working, hoping the default would be as you said works in the example):
In the log after starting up, I get these messages (among many others):
...
Mar 1, 2011 7:51:23 PM org.apache.solr.core.CoreContainer$Initializ
Hmm, okay, have to try to find time to install the example/multicore and
see.
It's definitely never worked for me, weird.
Thanks.
On 3/1/2011 2:38 PM, Chris Hostetter wrote:
: Unless I'm doing something wrong, in my experience in multi-core Solr in
: 1.4.1, you NEED to explicitly provide an a
: Unless I'm doing something wrong, in my experience in multi-core Solr in
: 1.4.1, you NEED to explicitly provide an absolute path to the 'data' dir.
have you looked at the example/multicore directory that was included in
the 1.4.1 release?
it has a solr.xml that loads two cores w/o specifying
I did try that, yes. I tried that first in fact! It seems to fall back
to a ./data directory relative to the _main_ solr directory (the one
above all the cores), not the core instancedir. Which is not what I
expected either.
I wonder if this should be considered a bug? I wonder if anyone has
Have you tried removing the tag from solrconfig.xml? Then it should
fall back to default ./data relative to core instancedir.
--
Jan Høydahl, search solution architect
Cominvent AS - www.cominvent.com
On 1. mars 2011, at 00.00, Jonathan Rochkind wrote:
> Unless I'm doing something wrong, in my
I spent a few hours chasing my tail on this one; I really just assumed
that the core's data dir would be under the core's instance dir. But I
ended up doing exactly what you did (copying from something I found on
the web).
seems like a design flaw that could be difficult to fix without breaki
13 matches
Mail list logo
