Hi, Danny:
Yes, 7.0-5 and 8.0-1 and following should have the accurate total on the last
page of search results where the last page has fewer results than the page
length.
Note that if the last page happens to have the same number of results as the
page length, the page can't be recognized as
One thing I discovered is that if I change search-option to unfiltered,
@total and the number of search results are both 88.
Regards,
Danny
On Tue, Jan 6, 2015 at 9:14 AM, Danny Sinang d.sin...@gmail.com wrote:
Hi Erik,
Here's the query and the options :
xquery version 1.0-ml;
import
Hi Erik,
Here's the query and the options :
xquery version 1.0-ml;
import module namespace search = http://marklogic.com/appservices/search;
at /MarkLogic/appservices/search/search.xqy;
declare option xdmp:mapping false;
declare variable $options :=
options
Hi, Danny:
Thanks for the additional information. The total is set to the estimate based
on the indexes.
That's pragmatic for pages other than the last page. In that case, we can
calculate an accurate total based on the start page, page length, and result
count.
I'll file a bug.
Erik
After running this filtered query :
*search:search($search, $options, 1, 100)*
I got */search:response/@total* = 88 despite there being only 36 search
results returned by the query.
The content source / database being queried does not have a fragment root
or parent.
What could I be doing
Hi, Danny:
Can you share your query and options?
Erik Hennum
From: general-boun...@developer.marklogic.com
[general-boun...@developer.marklogic.com] on behalf of Danny Sinang
[d.sin...@gmail.com]
Sent: Monday, January 05, 2015 1:44 PM
To: general
Subject:
