-
Notifications
You must be signed in to change notification settings - Fork 112
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] Searching multiple rollup indexes not working as expected #1265
Comments
From Opensearch 2.5 release notes: I upgraded my setup to 2.11, and retried the whole scenario and still having the same issue, i.e. it does not seem to be using all the rolled up indexes to get the results when I use a query via |
This is a show stopper for us. Given that the release notes says this is supported in 2.5 version, it will help if someone can check if I am missing something or if there are some known issues? Would love to see a working sample. |
Hi, we have a setting for this |
Thanks @tandonks It works. Will close this for now and reopen if i come across any further issues. |
What is the bug?
Searching multiple rollup indexes not working as expected.
How can one reproduce the bug?
Followed the example provided at Index rollups - OpenSearch Documentation
I do see Rollups for multiple indexes being created (rollup_ndx-metric-000001, rollup_ndx-metric-000002, rollup_ndx-metric-000003) and I am able to query them individually. But when I try to search multiple Rollups via the following way, it does not seem to be using all the rolled up indexes to get the results as I am not seeing the results as expected.
GET /rollup_ndx-metric-*/_search
Result:
But if I remove the match all query, I see the it is showing correct info in the total hits. If query is not working as expected, seems like rollup feature is unusable when we want to search/filter data via query
Result:
What is the expected behavior?
Expect the query to work.
What is your host/environment?
Do you have any screenshots?
If applicable, add screenshots to help explain your problem.
Do you have any additional context?
Add any other context about the problem.
The text was updated successfully, but these errors were encountered: