I really think you'll be in a world of hurt if you have the same
ID on different shards. I just wouldn't go there. The statement
"may be non-deterministic" should be taken to mean that this
is just unsupported.
Why is this the case? What is the use-case for putting the
same ID on different shard?
Hi,
I stumbled across this thread after running into the same question. The
answers presented here seem a little vague and I was hoping to renew the
discussion.
I am using using a branch of Solr 4, distributed searching over 12 shards.
I want the documents in the first shard to always be selected
I think the first one to respond is indeed the way it works, but
that's only deterministic up to a point (if your small index is in the
throes of a commit and everything required for a response happens to
be cached on the larger shard ... who knows ?)
On Mon, Aug 8, 2011 at 7:10 PM, Shawn Heisey
On 8/8/2011 4:07 PM, simon wrote:
Only one should be returned, but it's non-deterministic. See
http://wiki.apache.org/solr/DistributedSearch#Distributed_Searching_Limitations
I had heard it was based on which one responded first. This is part of
why we have a small index that contains the new
Only one should be returned, but it's non-deterministic. See
http://wiki.apache.org/solr/DistributedSearch#Distributed_Searching_Limitations
-Simon
On Sat, Aug 6, 2011 at 6:27 AM, Pooja Verlani wrote:
> Hi,
>
> We have a multicore solr with 6 cores. We merge the results using shards
> parameter
