[
https://issues.apache.org/jira/browse/UNOMI-1014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18131302#comment-18131302
]
Serge Huber commented on UNOMI-1014:
------------------------------------
Also linked: https://github.com/apache/unomi/pull/923 (was missing as a web
link; already Fixed).
Small follow-up for the _all vs getAllItemsCount assertions:
https://github.com/apache/unomi/pull/924
Related: UNOMI-1018 (OpenSearch date/range aggregate buckets).
> Aggregate queries with a condition return nothing
> -------------------------------------------------
>
> Key: UNOMI-1014
> URL: https://issues.apache.org/jira/browse/UNOMI-1014
> Project: Apache Unomi
> Issue Type: Bug
> Reporter: Serge Huber
> Priority: Major
> Fix For: unomi-4.0.0
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> h3. Summary
> The query API can count items by property value, for example how many
> profiles have each first name. When the request sends a condition (POST on
> /cxs/query/profile/ followed by the property name), Unomi answers with an
> empty response (HTTP 204). This happens with both Elasticsearch and
> OpenSearch. The server log shows an error while reading the result. The same
> request without a condition (GET), or with the optimized option, works.
> On Elasticsearch the problem is already present in 3.0.0 and 3.0.1. The goal
> of this ticket is that these queries return their results again on both
> search engines.
> h3. How to test
> On Elasticsearch and on OpenSearch, create a few profiles with known first
> names, then send a POST aggregate query on properties.firstName with a
> match-all condition. Check that the answer lists the expected counts. Do the
> same with the optimized option.
> Automated tests to add: an integration test, run on both search engines, that
> sends an aggregate query with a condition, with and without the optimized
> option, and checks the counts.
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)
