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
Query DSL: Allow to control if filters should be cached #181
Labels
Comments
Query DSL: Allow to control if filters should be cached, closed by bd6b89f. |
Hi kimchy - there is nothing about named caches in the docs |
I meant a field named |
williamrandolph
pushed a commit
to williamrandolph/elasticsearch
that referenced
this issue
Jun 4, 2020
mindw
pushed a commit
to mindw/elasticsearch
that referenced
this issue
Sep 5, 2022
MPC-2467: fix for lti * MPC-2467: fix for lti (and saml, but not sure if this would affect saml, depends on how deep the object goes); for importing from directory, merge of common and local yml data was not complete; ended up with missing properties for lti.admin.prefix and lti.class.prefix if these settings were default (ie only set in common.yml) * Merged master into bug/jj/ltiImportAdminjs_2021.08.08 Approved-by: Alan Nuchnoi
cbuescher
pushed a commit
to cbuescher/elasticsearch
that referenced
this issue
Oct 2, 2023
Since February 7 we noticed an increase in the 100th percentile service time of the `country_agg_cached` query in geonames when the trial license is enabled. In order to dig whether this is related to JVM activity (GC, safepoints) we temporarily enable GC logs. This is expected to be low-impact on performance but allows us to dig deeper. Relates elastic#181
This issue was closed.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add to the
contant_score
,filtered
queries, as well to thebool
filter field namedcache
allowing to control if filteres will be cached or not.The text was updated successfully, but these errors were encountered: