Hi Avlesh,
Avlesh Singh wrote:
1. Is it considered as good practice to set up several DIH request
handlers, one for each possible parameter value?
Nothing wrong with this. My assumption is that you want to do this to
speed
up indexing. Each DIH instance would block all others, once a
I guess SOLR-1352 should solve all the problems with performance. I am
working on one currently and I hope to submit a patch soon.
On Thu, Nov 12, 2009 at 8:05 PM, Sascha Szott sz...@zib.de wrote:
Hi Avlesh,
Avlesh Singh wrote:
1. Is it considered as good practice to set up several DIH
Hi all,
I'm using the DIH in a parameterized way by passing request parameters
that are used inside of my data-config. All imports end up in the same
index.
1. Is it considered as good practice to set up several DIH request
handlers, one for each possible parameter value?
2. In case the range
1. Is it considered as good practice to set up several DIH request
handlers, one for each possible parameter value?
Nothing wrong with this. My assumption is that you want to do this to speed
up indexing. Each DIH instance would block all others, once a Lucene commit
for the former is