You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe
In the backend of the new cache stats API, currently ICache implementations return a concrete class (ImmutableCacheStatsHolder) when providing a fixed snapshot of the cache's stats. We may want to refactor this to use an interface in case we want additional implementations later on.
Describe the solution you'd like
We could create an interface, possibly "CacheStats" or "CacheStatsResponse", which has similar logic of being aggregated by levels at creation time, and also implements Writeable and ToXContent. One downside is that serializing such an interface would be a bit messy, and might require writing class names into the StreamOutput or a similar approach.
Related component
Search:Performance
Describe alternatives you've considered
The status quo also works for now, but we might want to add this flexibility.
Additional context
No response
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe
In the backend of the new cache stats API, currently ICache implementations return a concrete class (ImmutableCacheStatsHolder) when providing a fixed snapshot of the cache's stats. We may want to refactor this to use an interface in case we want additional implementations later on.
Describe the solution you'd like
We could create an interface, possibly "CacheStats" or "CacheStatsResponse", which has similar logic of being aggregated by levels at creation time, and also implements Writeable and ToXContent. One downside is that serializing such an interface would be a bit messy, and might require writing class names into the StreamOutput or a similar approach.
Related component
Search:Performance
Describe alternatives you've considered
The status quo also works for now, but we might want to add this flexibility.
Additional context
No response
The text was updated successfully, but these errors were encountered: