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
Core: Rename caches #11569
Comments
++ |
One challenge here is that the new setting for the size of the query cache would be |
yeah we can't really... we can go to |
And |
we typically prefix the node level index related settings with How about
|
@bleskes That works for me, but the issue here is not the new name of the request cache, but the new name of the query cache (formerly known as filter cache) so that it would be different from the previous name of the request cache. |
@jpountz yeah, I got confused. The important part for me was to point out the usage of "indices." as node level settings which related to indices. As far as the name collision goes - I wonder how many people use the current query cache (i.e. shard requests caching) and thus how bad it would be to make a breaking change and change the semantics of that settings. Another alternative, which I'm on the fence about but think it's worth mentioning, is using the word segments in the name - as the queries are cached on a segment level. So that will be |
If there are no objections, I will try to implement Boaz's last proposal. |
++ |
In order to be more consistent with what they do, the query cache has been renamed to request cache and the filter cache has been renamed to query cache. A known issue is that package/logger names do no longer match settings names, please speak up if you think this is an issue. Here are the settings for which I kept backward compatibility. Note that they are a bit different from what was discussed on elastic#11569 but putting `cache` before the name of what is cached has the benefit of making these settings consistent with the fielddata cache whose size is configured by `indices.fielddata.cache.size`: * index.cache.query.enable -> index.requests.cache.enable * indices.cache.query.size -> indices.requests.cache.size * indices.cache.filter.size -> indices.queries.cache.size Close elastic#11569
In order to be more consistent with what they do, the query cache has been renamed to request cache and the filter cache has been renamed to query cache. A known issue is that package/logger names do no longer match settings names, please speak up if you think this is an issue. Here are the settings for which I kept backward compatibility. Note that they are a bit different from what was discussed on elastic#11569 but putting `cache` before the name of what is cached has the benefit of making these settings consistent with the fielddata cache whose size is configured by `indices.fielddata.cache.size`: * index.cache.query.enable -> index.requests.cache.enable * indices.cache.query.size -> indices.requests.cache.size * indices.cache.filter.size -> indices.queries.cache.size Close elastic#11569
With the merge of queries and filters, it would make sense to rename our caches:
I also have hopes that the latter renaming will help remove confusion that the request cache is short-lived since it is invalidated on every refresh.
The text was updated successfully, but these errors were encountered: