-
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
[Reporting] CSV Export should use ESE search strategy #110679
Comments
Pinging @elastic/kibana-app-services (Team:AppServices) |
I think the issue here is that you are consuming the |
CSV export uses the
|
Closing this issue as CSV export can not use the ESE_SEARCH_STRATEGY |
Kibana version: 7.x
See #109167 and #109976 for background context.
Kibana Reporting had an issue that using a SearchSource object serialized on the client, the SearchSource service on the server did not automatically handle the user's preference to include frozen indices in a search. Since a fix was needed urgently, the fix was implemented on the Reporting side. Reporting used its UISettings client to get the value of
search:includeFrozen
and pass that as an option todata.search
.SearchSource consumers should not have to provide configuration as additional options, since those options can be read internally in SearchSource. Fixing this issue in SearchSource reduces logic needed on the consumer side and promotes consistency from the user's perspective.
The text was updated successfully, but these errors were encountered: