-
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.x] Conditionally sets ignore_throttled only when search:includeFrozen is true #114381
[7.x] Conditionally sets ignore_throttled only when search:includeFrozen is true #114381
Conversation
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.
seems to work as advertised, thank you 👍 just left a small style question below
x-pack/plugins/infra/server/lib/adapters/framework/kibana_framework_adapter.ts
Show resolved
Hide resolved
Pinging @elastic/logs-metrics-ui (Team:logs-metrics-ui) |
@elasticmachine merge upstream |
@elasticmachine merge upstream |
@elasticmachine merge upstream |
💛 Build succeeded, but was flaky
Test FailuresKibana Pipeline / general / X-Pack API Integration Tests.x-pack/test/api_integration/apis/ml/jobs/categorization_field_examples·ts.apis Machine Learning jobs Categorization example endpoint - invalid, too many tokens.Standard Out
Stack Trace
Metrics [docs]
History
To update your PR or re-run it, just comment with: |
Fixes #113197
Summary
The "ignore_throttled" ES option is deprecated, as are frozen indices in general.. ES queries behave as though this flag is set to
true
by default, meaning they will ignore frozen indices.When the Kibana setting for "include frozen indices" is set to true, we still need to set this flag to
false
explicitly to continue to respect that Kibana setting. (Exact deprecation strategy for that Kibana setting is still TBD.)However, the current code was always setting the
ignore_throttled
option to be the!
-negated value of whatever thesearch:includeFrozen
setting was. Whenever this value is included in a query, an ES deprecation log is produced. When a user hasn't indicated that they are even trying to interact with the deprecated frozen index feature, we shouldn't be including this flag and setting it to its default value. We should leave the flag out altogether and avoid the deprecation log warning.To Test / Reproduce
?sourceId=deprecation_logs
, if you visit the Logs UI directly, you won't see them)