[
https://issues.apache.org/jira/browse/UNOMI-119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Serge Huber resolved UNOMI-119.
-------------------------------
Resolution: Fixed
Fix Version/s: 1.2.0-incubating
Fixed typo in Blueprint file that prevented default value from being used.
> pastEventCondition hardcoded 5000 limit
> ---------------------------------------
>
> Key: UNOMI-119
> URL: https://issues.apache.org/jira/browse/UNOMI-119
> Project: Apache Unomi
> Issue Type: Improvement
> Reporter: Don Hinshaw
> Assignee: Serge Huber
> Priority: Minor
> Fix For: 1.2.0-incubating
>
>
> https://<host>/cxs/query/profile/count
> {code}
> {
> "type": "pastEventCondition",
> "parameterValues": {
> "eventCondition" : {
> "type" : "matchAllCondition",
> "parameterValues" : {
> }
> },
> "numberOfDays" : 7
> }
> }
> {code}
> in ElasticSearchPersistenceServiceImpl.java like 1485 there is a hardcoded
> limit of 5000.
> {code}bucketsAggregation =
> AggregationBuilders.terms("buckets").field(aggregate.getField()).size(5000);{code}
> This change was made on December 5 in commit
> 96a018ecb1b5b907930504e69f6da9357db8385e
> I think this value should be configurable. The way it is now, we are unable
> to get the count when our query has more that 5000 results.
> Thanks.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
