You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What is the bug?
I have multiple rollup indices. E.g: rollup_logs-000001, rollup_logs-000002, ... one for each day
When I try to query these rollup indices, it only returns the data from the last index. Same as when I try to create a visualization.
If I query each index, the data returns correctly for each of them.
How can one reproduce the bug?
Steps to reproduce the behavior:
What is the expected behavior?
It should return data from all of the rollup indices
What is your host/environment?
Cloud Hosted: AWS Opensearch Service 2.7
Do you have any screenshots?
Result for querying "rollup_logs-000045"
Result for querying "rollup_logs-000046"
Finally, result for querying both "rollup_logs-000045,rollup_logs-000046". See how it says in the "shards": 6 successful, meaning it queried both indices but the result only from the 46
Do you have any additional context?
Add any other context about the problem.
The text was updated successfully, but these errors were encountered:
What is the bug?
I have multiple rollup indices. E.g: rollup_logs-000001, rollup_logs-000002, ... one for each day
When I try to query these rollup indices, it only returns the data from the last index. Same as when I try to create a visualization.
If I query each index, the data returns correctly for each of them.
How can one reproduce the bug?
Steps to reproduce the behavior:
What is the expected behavior?
It should return data from all of the rollup indices
What is your host/environment?
Do you have any screenshots?
Result for querying "rollup_logs-000045"
Result for querying "rollup_logs-000046"
Finally, result for querying both "rollup_logs-000045,rollup_logs-000046". See how it says in the "shards": 6 successful, meaning it queried both indices but the result only from the 46
Do you have any additional context?
Add any other context about the problem.
The text was updated successfully, but these errors were encountered: