On 09/03/2013 12:50 PM, Chris Hostetter wrote:
: like to understand how the ordering is defined so that I can compute an
: integer that is sorted in the same way. For example (shard "id" << 24) |
: docid or something like that.
If you want to ensure a consistent ordering, you have to index a
(u
: like to understand how the ordering is defined so that I can compute an
: integer that is sorted in the same way. For example (shard "id" << 24) |
: docid or something like that.
If you want to ensure a consistent ordering, you have to index a
(unique) value that you use as a secondary sort -
an explanation
for what you are seeing, or a guarantee that you will always see that
behavior?
-- Jack Krupansky
-Original Message- From: Michael Sokolov
Sent: Monday, September 02, 2013 7:42 PM
To: solr-user@lucene.apache.org
Subject: distributed query result order tie break question
Jack Krupansky
-Original Message-
From: Michael Sokolov
Sent: Monday, September 02, 2013 7:42 PM
To: solr-user@lucene.apache.org
Subject: distributed query result order tie break question
My question is about how query results are ordered in a distributed
query when sorting by "releva
My question is about how query results are ordered in a distributed
query when sorting by "relevance" and all the documents have the same
score, for example, when querying for "*:*".
It looks to me as if score ties are broken by shard and then within each
shard, by docid. So for example, if I
