Hi Tien
Consider using the export handler if you can. Then you have no paging.
When you are having a paging problem you might want to think of the use case --
how many of your users will be willing​ to page deeply? If they give up, then
you have lost already.
Cheers -- Rick
On May 29, 2017 7:58
Got it. The problem is tiebreakers. Consider two documents with the
same date. Whenever two documents are tied through all the sort
criteria you specify then the _internal_ Lucene document ID is used as
a tiebreaker.
The kicker is that doc1 and doc2 don't have the same internal IDs on
replica1 and
I think it's related to the sort clause: sort=position_posted_date_id, this
is happening only when documents have the same position_posted_date_id, I am
not sure what would be the default sort in this case, but depending on which
shards is handling the request, I am getting same result but sorted
d
Yes I am sure the uniqueKeyId are unique
Here are exactly my two requests:
http://SOLR_IP:8201/solr/Staging/select?q=*:*&rows=100&start=800&fl=id,position_id,job_id&sort=position_posted_date_id%20desc
http://SOLR_IP:8201/solr/Staging/select?q=*:*&rows=100&start=900&fl=id,position_id,job_id&sort=
Are you absolutely and totally sure that the s are unique
(id by default) when you say that the only difference is the date? It
sounds like you're somehow getting the same doc indexed with two (or
more) different IDs.
You can look at this by identifying some suspect IDs and issuing queries like
s
