-
Notifications
You must be signed in to change notification settings - Fork 114
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
[BUG] Unable to query across mutliple rollup indexes when rollup has been modified #1349
Comments
I found some time to work on a "minimal" reproduction, I might be able to reduce the code further but in this format it also demonstrates the original workflow (although rollups are managed though ISM policies). Posting the below into the Dev console and running each expression in sequnce, the error on the last query is the one demonstrating the issue.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What is the bug?
Back in 2023 we started using using rollup jobs to aggregate some data into year based indeces, so the data ends up in the indexes rollup-data-2023, rollup-data-2024 and rollup-data-2025. When visualising data from these indeces we have an index pattern
rollup-data-*
.Towards the end of 2024 we have added a field to the rollup job leading to the following scenario:
When performing a query for the new field against the individual indices we get the following (expected) behavour:
This is all understandable so far, the problem comes when trying to execute the same query against the index pattern that matches all three indices.
When doing this all 3 shards fail.
How can one reproduce the bug?
See description for now, I might try and create a smaller reproduction if more explanation is needed.
What is the expected behavior?
I would expect only one shard to fail, allowing us to create visualisations for the index pattern.
What is your host/environment?
The text was updated successfully, but these errors were encountered: