Gravatar for colema18@gmail.com

Question by colema18, Sep 21, 2015 12:08 PM

CoveoPager not supporting page 101 or higher?

Is this a known issue or am I doing something wrong. I had 2 CoveoPager elements on the page which makes clicking on the same page twice go back to the first page but even after I removed one of the pager elements page 101 chokes and goes back to page 1. Is there a reason for this?

UPDATE: More Info So it looks like I am getting a RequestedResultsMax error. Not sure why though, seems like it would just be returning the results of 1000 to 1010 and not 1010 results. Unless the JS Framework actually asks for the first 1010 results insteal of 1000 to 1010. Any direction would be helpful, below is the exception coming back from the REST call.

{
  "totalCount" : 0,
  "totalCountFiltered" : 0,
  "duration" : 12,
  "indexDuration" : 10,
  "requestDuration" : 7,
  "searchUid" : "2dfdba5f-aef8-49f7-95b9-4f5db874f004",
  "pipeline" : "default",
  "apiVersion" : 2,
  "exception" : {
    "code" : "RequestedResultsMax",
    "context" : null
  },
  "notifications" : [ ],
  "termsToHighlight" : { },
  "phrasesToHighlight" : { },
  "queryCorrections" : [ ],
  "groupByResults" : [ ],
  "results" : [ ]
}
1 Reply
Gravatar for mlaporte@coveo.com

Answer by Martin Laporte, Sep 22, 2015 3:53 AM

By default the index itself won't return more than the first 1000 results of a query, because the farther you go the more expensive it is to compute. On an on-premises / sitecore setup this can be changed in the Admin Tool. But I've rarely seen cases where it was useful to go beyond the first 2-3 pages anyway.

Ask a question