-
Notifications
You must be signed in to change notification settings - Fork 25.3k
Test: assert adjacency matrix cache #69440
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
Conversation
Adds an assertion that the adjacency matrix aggregation can hit the request cache even when the request contains a lookup style `terms` filter.
Pinging @elastic/es-analytics-geo (Team:Analytics) |
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.
Added a minor suggestion. Otherwise LGTM.
- do: | ||
indices.stats: { index: test, metric: request_cache} | ||
- match: { _shards.total: 1 } | ||
- match: { _all.total.request_cache.hit_count: 1 } |
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.
That game me a bit of a pause. Took me a bit to realize that you are asking for one index only in stats. I think it would have been clearer if it was indices.test.total.request_cache.hit_coun
instead of _all.total.....
Thanks for reviewing @imotov ! |
Adds an assertion that the adjacency matrix aggregation can hit the request cache even when the request contains a lookup style `terms` filter.
I believe there is an error in this one around caching. I've added the infrastructure to fix that error in #69439. |
Adds an assertion that the adjacency matrix aggregation can hit the
request cache even when the request contains a lookup style
terms
filter.