yes. This will make user think our search engine has some bug.
from the comments of the codes, it needs more things to do
if (prevShard != null) {
// For now, just always use the first encountered since we
can't currently
// remove the previous one added to the priority queue.
If we switched
// to the Java5 PriorityQueue, this would be easier.
continue;
// make which duplicate is used deterministic based on shard
// if (prevShard.compareTo(srsp.shard) >= 0) {
// TODO: remove previous from priority queue
// continue;
// }
}
2010/7/21 MitchK <mitc...@web.de>:
>
> Ah, okay. I understand your problem. Why should doc x be at position 1 when
> searching for the first time, and when I search for the 2nd time it occurs
> at position 8 - right?
>
> I am not sure, but I think you can't prevent this without custom coding or
> making a document's occurence unique.
>
> Kind regards,
> - Mitch
> --
> View this message in context:
> http://lucene.472066.n3.nabble.com/a-bug-of-solr-distributed-search-tp983533p983771.html
> Sent from the Solr - User mailing list archive at Nabble.com.
>
