-
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
[Timeseries] remove unused configuration properties #62543
Conversation
Pinging @elastic/kibana-app (Team:KibanaApp) |
I don't feel comfortable removing these in a minor version - if an installation still has these settings set, Kibana won't start for them. My suggestion:
This will have the following effect when a user still has these settings: Kibana will still start but log a warning that the setting is unused. With 8.0 we can remove the setting completely and add it to the breaking changes list. |
@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.
Tested the changes to the Rollup plugin locally, code LGTM.
This test failure is probably legit, the infra app has a dependency on the metrics/vis_type_timeseries plugin. The reference has to be renamed. |
ping @elastic/logs-metrics-ui |
@elasticmachine merge upstream |
# Conflicts: # x-pack/legacy/plugins/rollup/kibana.json
I tested this PR and it looks and works fine - one thing I noticed though is that if you just use @alexwizp what do you think about parking this PR till we moved the rest of timeseries over? This will very likely happen next week as there are no more blockers. |
@flash1293 np, let's parking it =) |
# Conflicts: # src/legacy/core_plugins/vis_type_timeseries/index.ts # x-pack/legacy/plugins/rollup/server/plugin.ts
💚 Build SucceededHistory
To update your PR or re-run it, just comment with: |
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, bye bye metrics
plugin
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.
Looks good from the infra
side
* [Timeseries] remove unused configuration properties * Fix PR comments * update id of vis_type_timeseries plugin * metrics -> vis_type_timeseries * fix wrong plugin id * update requiredPliugins for infra/kibana.json * change id * update plugin id in infra folder Co-authored-by: Elastic Machine <[email protected]>
* [Timeseries] remove unused configuration properties * Fix PR comments * update id of vis_type_timeseries plugin * metrics -> vis_type_timeseries * fix wrong plugin id * update requiredPliugins for infra/kibana.json * change id * update plugin id in infra folder Co-authored-by: Elastic Machine <[email protected]> Co-authored-by: Elastic Machine <[email protected]>
Dev-Docs
Mark
chartResolution
andminimumBucketSize
as deprecated configuration properties for TSVB 👋In #9725 TSVB visualization was added to Kibana. Also in this PR we can find that 2 configuration properties were declared:
chartResolution
andminimumBucketSize
. The problem is that until today no one has started using these properties, an implementation has not been added