[
https://issues.apache.org/jira/browse/UNOMI-1014?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Serge Huber updated UNOMI-1014:
-------------------------------
Description:
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.
was:
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) when Elasticsearch is used. The server log shows an error
while reading the result. The same request without a condition (GET), or with
the optimized option, works.
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.
h3. How to test
With Elasticsearch, 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 and on OpenSearch.
Automated tests to add: an integration test that runs an aggregate query with a
condition, with and without the optimized option, and checks the counts.
Summary: Aggregate queries with a condition return nothing (was:
Aggregate queries with a condition return nothing on Elasticsearch)
> 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
>
>
> 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
(v8.20.10#820010)
