[
https://issues.apache.org/jira/browse/UNOMI-119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16131880#comment-16131880
]
Serge Huber commented on UNOMI-119:
-----------------------------------
Hello,
Indeed this should be configurable, for example in the
etc/org.apache.unomi.elasticsearch.cfg file. Would that be an acceptable
solution for your needs ?
If so it should be relatively easy to change, simply add the property in the
file, and modify the blueprint file and the code to read the property. Would
you like to try contributing this ? Unfortunately I'm working on some other
changes on that same class right now so it's not easy for me to do this change
right now.
cheers,
Serge...
> 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
> Priority: Minor
>
> 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)
