On Mon, 2016-01-25 at 20:38 -0700, Shawn Heisey wrote:
> Very likely what's happening is that sometimes your shards are
> responding on a different timescale with each request, so the pieces
> that get combined into the final result set arrive in a different
> order. This causes the Java object containing the results to get
> populated in a different order.
But is should not. Deterministic sort order is essential for paging.
Standard score-based sorting uses the shard-ID as tie breaker. If I am
not mistaken, that happens in the MergeSortQueue in the TopDocs?
- Toke Eskildsen, State and University Library, Denmark
|