-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
[7.16] Remove usage of ignore_throttled
unless targeting frozen indices to avoid deprecation warning
#117980
Comments
Pinging @elastic/kibana-vis-editors @elastic/kibana-vis-editors-external (Team:VisEditors) |
Since it'll no longer be possible to search frozen indices without seeing a deprecation warning, is the recommendation going forward for users to unfreeze frozen indices and thus not relying on Btw I created an issue to track this on the APM board: #117991 |
@sqren The deprecation message from ES recommends switch to cold or frozen tiers:
|
…ndices to avoid deprecation warning Part of: elastic#117980
…ndices to avoid deprecation warning (elastic#118022) * [Timelion ]Remove usage of ignore_throttled unless targeting frozen indices to avoid deprecation warning Part of: elastic#117980 * add tests
…ndices to avoid deprecation warning (elastic#118022) * [Timelion ]Remove usage of ignore_throttled unless targeting frozen indices to avoid deprecation warning Part of: elastic#117980 * add tests
Pinging @elastic/kibana-app-services (Team:AppServicesUx) |
PR to clean up the Reporting area: #120671 |
@rudolf the Reporting PR has been merged and backported. This issue looks ready to close |
ignore_throttled
and frozen indices have been deprecated in 7.16 elastic/elasticsearch#77864As a result, sending
ignore_throttled=true
orignore_throttled=false
both generates deprecation warnings.To avoid noisy deprecation warnings over which the user has no control, Kibana should only include this parameter if searching over frozen indices (e.g.
ignore_throttled=false
because the Advanced Settingsearch:includeFrozen: true
), i.e. you should NOT sendignore_throttled: true
in the request, which is anyway the default behavior.Related #112621 #120043
The text was updated successfully, but these errors were encountered: