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

Index pattern fetching should be limited #56352

Closed
tylersmalley opened this issue Jan 29, 2020 · 1 comment
Closed

Index pattern fetching should be limited #56352

tylersmalley opened this issue Jan 29, 2020 · 1 comment
Assignees
Labels
bug Fixes for quality problems that affect the customer experience Feature:Data Views Data Views code and UI - index patterns before 8.0

Comments

@tylersmalley
Copy link
Contributor

We're currently making a call from the front-end to api/saved_objects/_find?per_page=10001&type=index-pattern which is being done here. This can result in a very large request, oven 10's of megabytes due to the field cache. We should request the index patterns as we need them, and limit the fields being requested. A similar effort was recently done with Lens.

@tylersmalley tylersmalley added bug Fixes for quality problems that affect the customer experience Team:AppArch labels Jan 29, 2020
@elasticmachine
Copy link
Contributor

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

@lukeelmers lukeelmers added the Feature:Data Views Data Views code and UI - index patterns before 8.0 label Jan 30, 2020
Dosant added a commit that referenced this issue Feb 5, 2020
Should address #56352.

I did a look up and it seems like only id and title a really used in case that savedObjectsCache is used. So I simply limited that request to fetch only title
Dosant added a commit to Dosant/kibana that referenced this issue Feb 5, 2020
Should address elastic#56352.

I did a look up and it seems like only id and title a really used in case that savedObjectsCache is used. So I simply limited that request to fetch only title
Dosant added a commit to Dosant/kibana that referenced this issue Feb 5, 2020
Should address elastic#56352.

I did a look up and it seems like only id and title a really used in case that savedObjectsCache is used. So I simply limited that request to fetch only title
@Dosant Dosant closed this as completed Feb 5, 2020
tylersmalley pushed a commit that referenced this issue Feb 5, 2020
Should address #56352.

I did a look up and it seems like only id and title a really used in case that savedObjectsCache is used. So I simply limited that request to fetch only title

Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>
tylersmalley pushed a commit that referenced this issue Feb 5, 2020
Should address #56352.

I did a look up and it seems like only id and title a really used in case that savedObjectsCache is used. So I simply limited that request to fetch only title

Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>
tylersmalley pushed a commit that referenced this issue Feb 6, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Fixes for quality problems that affect the customer experience Feature:Data Views Data Views code and UI - index patterns before 8.0
Projects
None yet
Development

No branches or pull requests

4 participants