That should be OK. The recursive bit happens when you define the shard
locations in your config files in the default search handler.
On Fri, Nov 2, 2012 at 6:42 AM, ravi.n wrote:
> Erick,
>
> We are forming request something like below for default /select request
> handler, will this cause an i
Erick,
We are forming request something like below for default /select request
handler, will this cause an issue?
So far we are not facing any recursive issues.
http://94.101.147.150:8080/solr/select/?q=*%3A*&version=2.2&start=0&rows=10&indent=on&shards=localhost:8080/solr/coll1,localhost:8080/so
Until you nail down what the user did, this is may cause
problems. A sharded system assumes that the unique IDs
in your schema exists on one and only one shard,
otherwise you'll be getting multiple copies of the docs.
And you've only shown a multi-core setup, NOT a sharded
setup. You need to defi
Erick,
Thanks for your response.
All the 7 folders are of same schema, i mean document structure is same. I
am not very sure how did customer get this data dump into different folders.
Now we have configured Solr with multicore, each core pointing to each
directory and using shards to get a single
How did you get the 7 directories anyway? From your message,
they sound like they are _solr_ indexes, in which case you
somehow created then with Solr. But I don't really understand
the setup in that case.
If these are Solr/Lucene indexes, you can use the "multicore"
features. This treats them lik
