We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Part of #61738
This is the current search logic flow chart:
To simplify implementation and segregate legacy code, we'd need to refactor the flow to become"
The key changes here are
batchSearches
SearchSource
defaultSearchStrategy
fetch
callClient
msearch
The text was updated successfully, but these errors were encountered:
Pinging @elastic/kibana-app-arch (Team:AppArch)
Sorry, something went wrong.
lizozom
Successfully merging a pull request may close this issue.
Part of #61738
This is the current search logic flow chart:
To simplify implementation and segregate legacy code, we'd need to refactor the flow to become"
The key changes here are
batchSearches
is enabled from withinSearchSource
(this code is to stick around until v8)defaultSearchStrategy
altogetherfetch
,callClient
andmsearch
to a LEGACY folder.batchSearches
is disabled, call data's search service directly fromSearchSource
, otherwise call LEGACY logicThe text was updated successfully, but these errors were encountered: