-
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.17] Vega functional tests fail when run against ES 8.0 #123134
Conversation
…109090) * [vega] Handle removal of deprecated date histogram interval Fixes: elastic#106352 * fix CI * add deprecation_interval_info * add test * Update vega_info_message.tsx * fix types * Update es_query_parser.ts * apply comments * fix error Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com> Co-authored-by: Uladzislau Lasitsa <vlad.lasitsa@gmail.com>
* Update VEGA docs for v8.0 * Update docs/user/dashboard/vega-reference.asciidoc Co-authored-by: Kaarina Tungseth <kaarina.tungseth@elastic.co> Co-authored-by: Kaarina Tungseth <kaarina.tungseth@elastic.co> Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
…ate_histogram aggregation (elastic#115001)
This is not a fix as the |
@elasticmachine merge upstream |
@elasticmachine merge upstream |
Pinging @elastic/kibana-vis-editors @elastic/kibana-vis-editors-external (Team:VisEditors) |
Tested and vega requests are re-written correctly to only use |
💚 Build Succeeded
Metrics [docs]Module Count
Async chunks
Page load bundle
History
To update your PR or re-run it, just comment with: cc @alexwizp |
Closes: #123081
Summary
This PR is a backport of #109090 , #112781, #115001
Reason for backporting:
When testing 7.17 Kibana against 8.0 Elasticsearch, we get some Vega-related failures from CI:
https://buildkite.com/elastic/kibana-7-dot-latest-es-8-dot-0-forward-compatibility/builds/15
In 7.17, basic Kibana functions are still expected to work when run against ES 8.0, because during an upgrade process users will upgrade ES first. So we need to identify any failures from these builds and determine if they are simply bugs in our tests, or legit issues that would be 7.17 blockers.