-
Notifications
You must be signed in to change notification settings - Fork 25k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cardinality agg on constant_keyword
fields returning zero in 8.9+
#99776
Labels
:Analytics/Aggregations
Aggregations
>bug
Team:Analytics
Meta label for analytical engine team (ESQL/Aggs/Geo)
Comments
ebeahan
added
>bug
:Analytics/Aggregations
Aggregations
needs:triage
Requires assignment of a team area label
labels
Sep 21, 2023
elasticsearchmachine
added
the
Team:Analytics
Meta label for analytical engine team (ESQL/Aggs/Geo)
label
Sep 21, 2023
Pinging @elastic/es-analytics-geo (Team:Analytics) |
elasticsearchmachine
removed
the
needs:triage
Requires assignment of a team area label
label
Sep 21, 2023
This is due to #92060, I think. indexTerms is null for a const_term field, returning |
kkrik-es
added a commit
to kkrik-es/elasticsearch
that referenced
this issue
Sep 22, 2023
const_keyword fields don't show up in the leafReader, since they have a const value. elastic#92060 modified the logic to return no results in case the leaf reader contains no information about the requested field in a cardinality aggregation. This is wrong for const_keyword fields, as they contain up to 1 distinct value. To fix this, we fall back to the old logic in this case that can handle const_keyword fields properly. Fixes elastic#99776
kkrik-es
added a commit
that referenced
this issue
Sep 25, 2023
* Fix cardinality agg for const_keyword const_keyword fields don't show up in the leafReader, since they have a const value. #92060 modified the logic to return no results in case the leaf reader contains no information about the requested field in a cardinality aggregation. This is wrong for const_keyword fields, as they contain up to 1 distinct value. To fix this, we fall back to the old logic in this case that can handle const_keyword fields properly. Fixes #99776 * Update docs/changelog/99814.yaml * Update skip ranges for broken releases.
kkrik-es
added a commit
to kkrik-es/elasticsearch
that referenced
this issue
Sep 25, 2023
* Fix cardinality agg for const_keyword const_keyword fields don't show up in the leafReader, since they have a const value. elastic#92060 modified the logic to return no results in case the leaf reader contains no information about the requested field in a cardinality aggregation. This is wrong for const_keyword fields, as they contain up to 1 distinct value. To fix this, we fall back to the old logic in this case that can handle const_keyword fields properly. Fixes elastic#99776 * Update docs/changelog/99814.yaml * Update skip ranges for broken releases.
elasticsearchmachine
pushed a commit
that referenced
this issue
Sep 25, 2023
* Fix cardinality agg for const_keyword const_keyword fields don't show up in the leafReader, since they have a const value. #92060 modified the logic to return no results in case the leaf reader contains no information about the requested field in a cardinality aggregation. This is wrong for const_keyword fields, as they contain up to 1 distinct value. To fix this, we fall back to the old logic in this case that can handle const_keyword fields properly. Fixes #99776 * Update docs/changelog/99814.yaml * Update skip ranges for broken releases.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
:Analytics/Aggregations
Aggregations
>bug
Team:Analytics
Meta label for analytical engine team (ESQL/Aggs/Geo)
Elasticsearch Version
8.9.0+
Installed Plugins
No response
Java Version
bundled
OS Version
all
Problem Description
Beginning in 8.9.0, observing cardinality aggs returning zero against
constant_keyword
mapped fields.Steps to Reproduce
Performed simple setup of an index with
constant_keyword
mapping for fieldtest
in 8.8.2 and 8.9.0:8.8.2 result
8.9.0 result
Also see a zero value when querying
constant_keyword
values across indices:Logs (if relevant)
No response
The text was updated successfully, but these errors were encountered: