Nope. Problem is that the tie breaker is the internal Lucene Doc id. Which
a long time ago was invariant, that is a document indexed later always had
a larger internal doc id. But the various merge policies can combine
segments such that the internal IDs can change relative to one another
So
On Sun, Feb 3, 2013 at 7:46 AM, Erick Erickson erickerick...@gmail.com wrote:
Nope. Problem is that the tie breaker is the internal Lucene Doc id. Which
a long time ago was invariant, that is a document indexed later always had
a larger internal doc id. But the various merge policies can
Hi list,
I recognized that the result order is FIFO if documents have the same score.
I think this is due to the fact that documents which are indexed later get a
higher
internal document ID and the output for documents with the same score starts
with the lowest internal document ID and raises.
