Hi, I'm moving from es 6.x to 7.x, find the new feature data stream and would like to have a try.
But I'm a bit worried of the search performace for the docs explains When you submit a read request to a data stream, the stream routes the request to all its backing indices.doc source
Say we have a data stream alias as audit_log, consisting of hundreds of backing indices:
Can this search request only route to the several backing indices cause of the @timestamp range clause ?
Technically no, but in practice ES achieves this goal anyway: it routes the search to every backing index but the ones that don't match the timestamp range get optimised into a MatchNoDocsQuery which obviously hits no data and takes no time to execute.
Thank you David. I am still curious that is this a feature of backing indices or of filter cache?
I mean would it be slow at the first search query and slow when not hit time span filter cache? For that common time series search cases always changed time span frequently.
This happens when rewriting the query into its optimised form, long before the filter cache gets involved. It involves comparing two long timestamp values, which is almost instantaneous and doesn't involve any caching.
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.