-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
[Search] Unify search plugin step 3 — Rollup search strategy #98122
Conversation
Pinging @elastic/kibana-app-services (Team:AppServices) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Overall look good.
Added a couple of comments.
src/plugins/data/server/search/strategies/rollup_search/rollup_search_strategy.ts
Show resolved
Hide resolved
src/plugins/data/server/search/strategies/rollup_search/rollup_search_strategy.test.ts
Show resolved
Hide resolved
src/plugins/data/server/search/strategies/rollup_search/rollup_search_strategy.test.ts
Outdated
Show resolved
Hide resolved
src/plugins/data/server/search/strategies/ese_search/ese_search_strategy.test.ts
Show resolved
Hide resolved
@elasticmachine merge upstream |
# Conflicts: # docs/development/plugins/data/public/kibana-plugin-plugins-data-public.searchinterceptor.getserializableoptions.md # src/plugins/data/public/public.api.md
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If you try viewing a rollup index in discover, it now uses the wrong strategy and fails.
This happens because of the changes introduced by #91517.
See src/plugins/discover/public/application/helpers/update_search_source.ts:57
.
@lizozom, could take another closer look, please 🙏 I compared behavior with master and it seems to me it is the same.
|
@elasticmachine merge upstream |
# Conflicts: # src/plugins/data/server/search/strategies/ese_search/ese_search_strategy.ts
@kertal, that is the question I wanted to ask you, and also would like @lizozom to double-check (#98122 (review)) 🙏 I have very limited knowledge of how that part should work in Discover, but from what I see it look like either this pr works as expected or we have a bug in the main branch. |
Also not sure about this (tested rollups with this PR and it seemed to work), and you know #96766 is around the corner, which changes tons of stuff here. So the question is, what should be sent, and ideally after #96766 we could adapt it. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't see #96766 changing the behavior of setPreferredSearchStrategyId
, so I don't think these two PRs are related in this sense.
I now understand why discover
fetches documnets with the default
strategy, regardless of the index type - because it only needs the raw documents, without any aggs.
LGTM!
@elasticmachine merge upstream |
💚 Build SucceededMetrics [docs]Module Count
Public APIs missing comments
Page load bundle
History
To update your PR or re-run it, just comment with: |
@Dosant should this be closed ? |
Let's revisit this later |
Summary
Partially addresses #92802
As part of unifying the search plugin, we agree that we want to move rollup search into a separate search strategy.
Before this PR:
This PR:
Still
TODO
In separate pr:search/session
to data (blocked bysecurity
andtaskManager
, at this point teams have no plans to moving them)Checklist
Delete any items that are not applicable to this PR.
For maintainers