On Tue, Mar 9, 2010 at 7:00 PM, Clinton Gormley firstname.lastname@example.org:
If you can give an example of what you try and configure, then I can
probably give a better answer. I tried and explain it here:
what specifically do you struggle with so I can explain it better in
Yeah sorry, crap question
OK, for instance, do the following settings make sense. I realise that
some are the same as the defaults (and thus redundant) but I wanted to
be sure that I was putting them in the right place.
The store one is wrong, and I would play with the bufferSize as well:
Of course, when I create an index, I can set the gateway.fs.location to
a different directory, which would make sense, no?
Depends. When you explicitly set the one for the index, then you need to
make sure that you don't have two indices pointing to the same location. If
you don't specify one, then the global gateway location will be used, with
the index name appended as a sub directory. So I would say just leave the
global one to be fs, and let the index level ones "inherit it" (the index
will automatically use fs gateway if the global gateway is fs).
For things like mappings, would/could you put them in the config file,
would you just put_mapping via the API?
Currently, you can only place do it through the API. There is no option for
the cluster to start up and read mappings from a specific location. Of
course, there is also the question of which mappings in such a case apply to
Web Announcements Limited is a company registered in England and Wales,
with company number 05608868, with registered address at 10 Arvon Road,
London, N5 1PR.