Skip to content
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

[data.search.searchSource]: Expose SearchSource on server #65069

Closed
28 tasks done
ppisljar opened this issue May 4, 2020 · 2 comments · Fixed by #78383
Closed
28 tasks done

[data.search.searchSource]: Expose SearchSource on server #65069

ppisljar opened this issue May 4, 2020 · 2 comments · Fixed by #78383
Assignees
Labels
Feature:Search Querying infrastructure in Kibana Project:Alerting

Comments

@ppisljar
Copy link
Member

ppisljar commented May 4, 2020

In order to support expressions on the server we need searchsource available there.

Blocks: #65067

Blocked by:

Prep for cutover:

Cutover:

@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-app-arch (Team:AppArch)

@tsullivan
Copy link
Member

tsullivan commented Jul 13, 2020

@elastic/kibana-reporting-services needs this enhancement to provide a better CSV export implementation.

Currently we must take all the all, or almost all, of the search query used in the browser and pass it through the CSV export generation API. To provide better integration, we need to simply pass the ID of the saved search through the generation API. This enhancement would allow us to achieve that simpler architecture.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Feature:Search Querying infrastructure in Kibana Project:Alerting
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants