You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Looking at the deprecation logs for a running ES7 cluster, the only messages are the following:
[2020-01-16T23:20:05,749][WARN ][o.e.d.c.ParseField ] Deprecated field [cutoff_frequency] used, replaced by [you can omit this option, the [multi_match] query can skip block of documents efficiently if the total number of hits is not tracked]
[2020-01-16T23:20:23,850][WARN ][o.e.d.c.ParseField ] Deprecated field [cutoff_frequency] used, replaced by [you can omit this option, the [match] query can skip block of documents efficiently if the total number of hits is not tracked]
Looks like after all the work we did to use cutoff_frequency, it's basically no longer needed in ES7. We might as well remove it if we get the chance.
The text was updated successfully, but these errors were encountered:
just wanted to check this was safe to remove and the answer is yes, es6 and below will suffer a perf regression but we no longer support those versions so it's safe to remove.
Looking at the deprecation logs for a running ES7 cluster, the only messages are the following:
Looks like after all the work we did to use
cutoff_frequency
, it's basically no longer needed in ES7. We might as well remove it if we get the chance.The text was updated successfully, but these errors were encountered: