-
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
[vega] Handle removal of deprecated date histogram interval #109090
Conversation
@elasticmachine merge upstream |
@alexwizp there are some cases that we are not bwc, for example, if I add as interval "month" or "day". |
Pinging @elastic/kibana-app (Team:KibanaApp) |
@elasticmachine merge upstream |
@elasticmachine merge upstream |
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.
app services changes LGTM
src/plugins/vis_type_vega/public/components/vega_info_message.tsx
Outdated
Show resolved
Hide resolved
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.
LGTM!
cc @ghudgins this is not so urgent as it will be merged for 8.0 but maybe you want to play with it |
@elasticmachine merge upstream |
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.
It works fine and we keep this interval and auto_interval logic. By keeping this, it means that we support something that is not supported anymore by ES (the interval
param). We have discussed it with the team and we prefer this solution rather than not being bwc. (maybe it makes sense a brief mention in our docs)
My only concern is the usage of auto_date_histogram
in the default spec. As soon as we are keeping the interval setting, I think the default spec should stay as it is and provide an example of the auto_interval
usage (explicit vega variable). Another reason to not use the auto_date_histogram
in our default spec is that is doesn't support yet extended_bounds
.
From the other hand, If we don't want to "advertise" the interval setting then the default spec should use the auto_date_histogram
.
I don't have a strong opinion tbh. I would like your feedback on this one @flash1293 @ghudgins.
Synced offline with the team, we will proceed with the existing default spec that uses the interval and extended_bounds properties. |
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.
Code LGTM, tested it locally in Chrome. I think we have done the best we could here.
The only thing remaining is to mention this in vega docs but I can do it on a separate PR
@elasticmachine merge upstream |
💚 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 |
@alexwizp I removed the v7.16 label, this is only for 8 :D |
…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>
* [vega] Handle removal of deprecated date histogram interval (#109090) * [vega] Handle removal of deprecated date histogram interval Fixes: #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> * Updates the VEGA docs for v8.0 (#112781) * 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> * [Vega] Replacing the 'interval' property should only happen for the date_histogram aggregation (#115001) Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com> Co-authored-by: Uladzislau Lasitsa <vlad.lasitsa@gmail.com> Co-authored-by: Stratoula Kalafateli <efstratia.kalafateli@elastic.co> Co-authored-by: Kaarina Tungseth <kaarina.tungseth@elastic.co>
Fixes: #106352 Closes: #106657
Summary
This PR is created as a sample solution for #106352. I suggest, implicitly for the user, to change the
interval
field to the value corresponding to the current interval. Other visualizations work the same way.Plus, this solution is backward compatible with older
vega
specs. We shouldn't think about the complex solutions described in #106352 (comment)What options are supported:
The last three are automatically converted to
fixed_interval
/calendar_interval