-
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
removing old point series defaults #11958
removing old point series defaults #11958
Conversation
Does this fix this issue too? #11953. I notice they both reference the y-axis. |
jenkins, test this |
0db0b5a
to
c0ef67e
Compare
@@ -20,6 +20,7 @@ export function VislibVisTypeVislibVisTypeProvider(Private) { | |||
const updateIfSet = (from, to, prop, func) => { | |||
if (from[prop]) { | |||
to[prop] = func ? func(from[prop]) : from[prop]; | |||
delete from[prop]; |
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.
Cool thanks for fixing this!
Minor, unrelated to this PR feedback - I think a comment for this updateParams function would be helpful. It was hard for me to figure out what was it was for. :) Plus then at some point way down the line if we stop supporting pre 5.2 we can get rid of the code.
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.
I would like to see the comment added in this PR.
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 is there @archanid
d18a52a
to
03cf6a7
Compare
I'm new to this piece of code. Can someone explain why we designed it this way, with two objects containing point series defaults, one with old, one with new? |
@@ -14,12 +14,14 @@ export function VislibVisTypeVislibVisTypeProvider(Private) { | |||
const pointSeries = Private(AggResponsePointSeriesProvider); | |||
const VislibRenderbot = Private(VislibVisTypeVislibRenderbotProvider); | |||
|
|||
// converts old config format (pre 5.2) to the new one |
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.
@archanid ... i was refering to this comment
@archanid what exactly are you referring to with two objects (old and new) ? ... can you point to the code pls ? generally there is just one defaults object (for each vis type), which we changed quite a bit in 5.2, thats why |
Hello, Is the 5.4.1 version available to be used along with docker ? Thank you |
hi @Wassim24, when Kibana 5.4.1 will be released, it will be available as a docker image. Instructions to pull it can be found here https://www.elastic.co/guide/en/kibana/current/_pulling_the_image.html. For future reference, more general questions like yours are more suitable for the Q&A forums over at discuss.elastic.co/c/kibana. Use github for bug reports and feature requests, thanks. |
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.
wrt. #11954: it doesn't seem to work with visualizations which were created before this PR. The correct scaling method is not applied in the dashboard.
It does work when creating a new visualization from scratch.
Any ideas? It will require people to recreate their charts. Not that big of a deal, but wondering why this is happening.
wrt. #11953. This works!
@thomasneirynck fixed, works now with charts created before this PR as well |
fce26bc
to
0e84bc5
Compare
adba89b
to
0799227
Compare
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.
I verified that it now works for different line-modes and for percentage display on dashboards, and that older saved objects display correctly.
I would not backport this to 5.5 until a new release is cut. This is not all that trivial of a fix, and there is a risk that it runs afoul of issues related to upgrading (e.g. Beats dashboards), things that are harder to catch here in isolation.
it is quite nasty bug that will prevent ppl from using vislib charts on dashboards .... (auch !) |
this does not fix the fontSize issue when the visualization is opened individually in the Visualize app. This requires a refresh. The UI element does not update as expected. |
This fixes issues where properties from the visualizations saved in older versions were not applied to the Visualization. This also addressed the fontSize of metrics not being applied on the Dashboard.
This fixes issues where properties from the visualizations saved in older versions were not applied to the Visualization. This also addressed the fontSize of metrics not being applied on the Dashboard.
@ppisljar can you do the backport to 5.4? There are some merge conflicts (because gauge and metric don't exist on those branches) and don't want to resolve issues the wrong way |
I use Kibana 5.6.3 and still have the problem with my heatmaps, even when recreated. Maybe not related to this defect, but the feature seems almost completely broken : linear, log, square root, are all linear with different boundaries. |
fixes #11954, #11953, #12437
the old point series defaults were not removed and were causing the new properties to be overridden