Hi Erick,"You still haven’t given an example of the results you’re seeing
that are unexpected".
I will give an example of the data I received. Before starting data update I
have:
solrCloud: Expected series criteria:386062
Collected series: 386062
Number of requests: 40
Collected unique series: 3
I said nothing about docId changing. _any_ sort criteria changing is an issue.
You’re sorting by score. Well, as you index documents, the new docs change the
values used to calculate scores for _all_ documents will change, thus changing
the sort order and potentially causing unexpected results w
Hi, Erick
I have a python script that sends requests with CursorMark. This script
checks data against the following Expected series criteria:
Collected series:
Number of requests:
Collected unique series:
The request looks like this:
select?indent=off&defType=edismax&wt=json&facet.query={!key=
Define “incorrect” please. Also, showing the exact query you use would be
helpful.
That said, indexing data at the same time you are using CursorMark is not
guaranteed do find all documents. Consider a sort with date asc, id asc. doc53
has a date of 2001 and you’re already returned the doc.
Ne
Good afternoon,
Could you please suggest us a solution: during data updating process in
solrCloud, requests with cursor mark return incorrect data. I suppose that
the results do not follow each other during the indexation process, because
the data doesn't have enough time to be replicated betwe
Good afternoon,
Could you please suggest us a solution: during data updating process in
solrCloud, requests with cursor mark return incorrect data. I suppose that
the results do not follow each other during the indexation process, because
the data doesn't have enough time to be replicated betwe
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
Hello,
I group search result by a field (with high cardinality)
I paginate search page using num of groups using param group.ngroups=true.
But that cause high CPU issue. So i turn off it.
Without ngroups=true, i can't get the num of groups so pagination is not
correct because i must use numFound,
erently.
>
> When adding a second sort by id like this
> sort=position_posted_date_id%20desc,id%20desc, the issue is no longer
> happening.
>
> Thanks
>
>
>
> --
> View this message in context:
> http://lucene.472066.n3.nabble.com/Pagination-issue-tp4308226p4308310.html
> Sent from the Solr - User mailing list archive at Nabble.com.
orted
differently.
When adding a second sort by id like this
sort=position_posted_date_id%20desc,id%20desc, the issue is no longer
happening.
Thanks
--
View this message in context:
http://lucene.472066.n3.nabble.com/Pagination-issue-tp4308226p4308310.html
Sent from the Solr - User mailing
erent result through the
exactly two same request.
Thank you for your help
--
View this message in context:
http://lucene.472066.n3.nabble.com/Pagination-issue-tp4308226p4308297.html
Sent from the Solr - User mailing list archive at Nabble.com.
ight difference a few ms.
>
> Please, can you help us to figure out what is happening ?
> thank you
>
>
>
> --
> View this message in context:
> http://lucene.472066.n3.nabble.com/Pagination-issue-tp4308226.html
> Sent from the Solr - User mailing list archive at Nabble.com.
message in context:
http://lucene.472066.n3.nabble.com/Pagination-issue-tp4308226.html
Sent from the Solr - User mailing list archive at Nabble.com.
13 matches
Mail list logo