-
Notifications
You must be signed in to change notification settings - Fork 24.9k
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
TSDB: terms query with order by top_metrics on a counter field reports null values when applied on mixed index (non-TSDB rolled over to TSDB) #96192
Comments
Pinging @elastic/es-analytics-geo (Team:Analytics) |
@dej611 Is it possible to add an ES reproduction? I'm wondering whether what documents exist in the two indices that match with the range filter. This could explain why the pie chart renders differently. |
@tetianakravchenko created the environment where I managed to reproduce the issue. |
I tried to reproduce the issue unsuccessfully using the following YAML test which does the following:
I see the same results. For this reason I think the issue might be rollover-related.
|
I did another test introducing a rollover operation for one of the non-time series indices but still I am not able to reproduce the issue.
|
Pinging @elastic/es-storage-engine (Team:StorageEngine) |
Elasticsearch Version
8.8.0-SNAPSHOT
Installed Plugins
No response
Java Version
bundled
OS Version
Darwin -- 21.6.0 Darwin Kernel Version 21.6.0: ; root:xnu-8020.240.18.700.8~1/RELEASE_ARM64_T6000 arm64
Problem Description
This issue can be reproduced on a index which was originally non-TSDB then migrated to TSDB.
This happens when using the k8s integration package in kibana.
When sending a
terms
agg using atop_metrics
with a counter field to order results, depending on the selected time range results vary from correct tonull
:null
values are returnedNo shards failures reported.
Steps to Reproduce
More details with query can be found in this Kibana issue: elastic/kibana#157839 (comment)
Logs (if relevant)
No response
The text was updated successfully, but these errors were encountered: