-
Notifications
You must be signed in to change notification settings - Fork 8.2k
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
Limit fetching index patterns #56603
Limit fetching index patterns #56603
Conversation
It relies in implementation details, but better then nothing
Pinging @elastic/kibana-app-arch (Team:AppArch) |
ack, reviewing this evening. |
Thanks for jumping on this so quickly! At first I was excited by the limited scope required for this fix, but the more I dug into it the more I believe the change required to be a bit more involved. Looking at the get method alone in the
There might be something I am missing here, as I am unable to find a broken path and there do not appear to be any functional tests effected. |
As I understood it, there are 2 different types of cache.
|
@elasticmachine merge upstream |
💚 Build SucceededHistory
To update your PR or re-run it, just comment with: |
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.
Looking like these changes should help, two minor nit's
@Dosant, multiple index pattern cache types for the same class, that's wild - knew I was missing something, thanks for the explanation. |
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.
This looks good to me. Tested Chrome OSX and nothing seems broken from what I can tell.
@Dosant is correct; There are two types of caches and the one that was touched here has very limited use (mainly for the index pattern select dropdown in discover AFAIK).
expect(savedObjectsClient.find).toHaveBeenCalledTimes(1); | ||
}); | ||
|
||
test('can refresh the saved objects caches', async () => { |
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.
Thanks for adding these 🙏
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
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
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>
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>
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
Summary
Should address #56352.
I did a look up and it seems like only
id
andtitle
a really used in case thatsavedObjectsCache
is used. So I simply limited that request to fetch onlytitle
Checklist
Use
strikethroughsto remove checklist items you don't feel are applicable to this PR.For maintainers