i send a ids filter to es ,the took in response is average of 30,but when replace by ids query,the took is 1 or 2.
why?
That won't be an issue anymore with 2.x as query and filters are now merged.
The difference is probably due to scoring computation for queries which is not the case for filters.
Plus filters can be cached. Not queries
thank you for your reply, but i can't understand why query is faster,if you can provide some url to explain this case? thank you
I misread your original post. Sorry.
Do you have the exact same response time (order of magnitude) when you restart the node before running each query?
I think it's related to the cache.
thank you for your reply ,maybe in this case ,query is enough and we have choose query not filter .
can you solve our' a other problemlink
our produce cluster upgrade to 1.7.4 from 1.5.2 yesterday,but problem happen