In our setup, we handle the document distribution and uniqueness across
> cores outside of Solr.
>
> --
> Hector
>
> On Jan 11, 2012, at 1:53 AM, shlomi java wrote:
>
> > Straying a bit from the subject,
> >
> > don't you think it will be useful to have th
Straying a bit from the subject,
don't you think it will be useful to have the shards parameter used also in
the index, in order to maintain document uniqueness?
I mean as an out of the box feature of Solr.
Because the situation today is that a Solr's client working with a sharded
Solr is respons
If you want to randomly distribute requests across shards, then I think
it's a case of Replication.
In Replication setup, all cores have the same schema AND data, so query any
core should return the same result. It is used to support heavy load. Of
course such setup will required some kind of load
hola,
1) When distributing search across several Shards, is the merged result
reflects the overall ranking, cross-shards?
I'm talking about stuff like "document frequency".
I guess it does, otherwise distributed search wouldn't have overhead.
talking about overhead,
2) is there a known ratio of t
hi community,
I understand that optimize builds a NEW index from the live one, and then
swaping them.
And that it is best to schedule optimize with care.
Can we still update and query the live index while optimize is on the go?
Or is the live index being locked during optimize?
10X
shlomiJ
