[
https://issues.apache.org/jira/browse/UNOMI-1020?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Serge Huber updated UNOMI-1020:
-------------------------------
Affects Version/s: unomi-4.0.0
unomi-3.0.1
> Aggregate _filtered count is approximate above 10,000 matches on the
> optimized path
> -----------------------------------------------------------------------------------
>
> Key: UNOMI-1020
> URL: https://issues.apache.org/jira/browse/UNOMI-1020
> Project: Apache Unomi
> Issue Type: Bug
> Affects Versions: unomi-4.0.0, unomi-3.0.1
> Reporter: Serge Huber
> Assignee: Serge Huber
> Priority: Major
> Fix For: unomi-4.0.0
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> h3. In short
> Above 10,000 matches, some reports show the wrong number of matches, usually
> too low (for example goal reports split by category).
> h3. Details
> * On the optimized aggregate path, {{_filtered}} comes from the search hit
> count, which stops at 10,000.
> * Above that, Unomi uses the sum of the returned buckets instead, which is
> wrong when the bucket limit drops values or ranges overlap.
> h3. Fix and test
> Count hits exactly on both aggregate paths. With more than 10,000 matches,
> {{_filtered}} must equal {{queryCount}} on both engines.
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)
