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.

Sign up for GitHub

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

Jump to bottom

[Index patterns] Remove fields cache in a migration #98383

Closed
wylieconlon opened this issue Apr 26, 2021 · 3 comments
Closed

[Index patterns] Remove fields cache in a migration #98383

wylieconlon opened this issue Apr 26, 2021 · 3 comments
Labels
Feature:Data Views Data Views code and UI - index patterns before 8.0 impact:low Addressing this issue will have a low level of impact on the quality/strength of our product. loe:small Small Level of Effort performance technical debt Improvement of the software architecture and operational architecture

Comments

@wylieconlon
Copy link
Contributor

wylieconlon commented Apr 26, 2021 •
edited
Loading

All direct access to the fields cache is removed in Kibana code, so the next step would be to remove this parameter in a migration. This will reduce the size of saved objects.

Meta issue: #84352
@wylieconlon wylieconlon added technical debt Improvement of the software architecture and operational architecture Feature:Data Views Data Views code and UI - index patterns before 8.0 Team:AppServices labels Apr 26, 2021
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-app-services (Team:AppServices)

@mattkime mattkime mentioned this issue May 12, 2021
Closed
63 tasks
@exalate-issue-sync exalate-issue-sync bot added impact:low Addressing this issue will have a low level of impact on the quality/strength of our product. loe:small Small Level of Effort labels Jun 21, 2021
@marius-dr marius-dr mentioned this issue Jul 30, 2021
Merged
@mattkime
Copy link
Contributor

mattkime commented Apr 1, 2022

I think this is best put on hold while the process of migration is reconsidered without downtime.

@lizozom
Copy link
Contributor

lizozom commented Apr 18, 2022

@mattkime Should we maybe close this issue in the meanwhile?
Or do you think this is useful for tracking?

@exalate-issue-sync exalate-issue-sync bot reopened this Apr 30, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Feature:Data Views Data Views code and UI - index patterns before 8.0 impact:low Addressing this issue will have a low level of impact on the quality/strength of our product. loe:small Small Level of Effort performance technical debt Improvement of the software architecture and operational architecture
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@mattkime @wylieconlon @lizozom @elasticmachine