superset icon indicating copy to clipboard operation
superset copied to clipboard

after upgrade superset 2.0 cant render a chart with event annotation on dashboard

Open oleg-savko opened this issue 2 years ago • 8 comments

After upgrading superset to 2.0, it cant render a chart with Event Annotation on dashboard and return:

Unexpected error
An error occurred while rendering the visualization: TypeError: Cannot use 'in' operator to search for 'columns' in undefined

Screenshot 2022-07-25 at 13 37 28

Screenshot 2022-07-25 at 13 43 23

If remove annotation chart render properly.

Expected: chart with event annotation worked as before.

oleg-savko avatar Jul 25 '22 10:07 oleg-savko

I confirm this issue after upgrading from from 1.5.1 to 2.0, annotations cannot be rendered. In my case, I use an annotation layer which results in the same error as shown above.

when hiding the annotation, the charts render just fine.

sowo avatar Jul 26 '22 16:07 sowo

Yes, have faced this issue as well :( As for now we are not able to migrate to version 2.0 just because a lot of charts use annotations.

alexey-kasiyanik avatar Jul 27 '22 12:07 alexey-kasiyanik

hi everyone! just a friendly ping here to check if there is any update about this issue

xmnlab avatar Aug 11 '22 12:08 xmnlab

Hello, any updates on this issue?

joaocmd93 avatar Aug 30 '22 19:08 joaocmd93

Workaround: On the chart, if you remove the annotations and re-add them back, the error should go away and will load correctly. Or you can click 'apply' and save the annotation and it will work.

The GET call to 'api/v1/chart/CHART_ID' is returning error 404.

1-Tyler avatar Sep 09 '22 17:09 1-Tyler

Workaround: On the chart, if you remove the annotations and re-add them back, the error should go away and will load correctly. Or you can click 'apply' and save the annotation and it will work.

The GET call to 'api/v1/chart/CHART_ID' is returning error 404.

For me this only works on the 1st load after reapplying the annotation. If I save and try to load again the error continues.

joaocmd93 avatar Sep 09 '22 17:09 joaocmd93

Ah you are right @joaocmd93 , I am seeing that behavior as well unfortunately.

1-Tyler avatar Sep 09 '22 18:09 1-Tyler

Facing the same error here 😭

bonamim avatar Sep 16 '22 14:09 bonamim

We also did an upgrade and users are facing this issue with some critical dashboards. Is there any solution to it yet? If no, we have to roll back to our previous version.

zhaorui2022 avatar Sep 21 '22 00:09 zhaorui2022

This seems to be the fix https://github.com/apache/superset/pull/20651 We did a cherry pick and it fixes our dashboards.

zhaorui2022 avatar Sep 21 '22 01:09 zhaorui2022

nice!

xmnlab avatar Sep 21 '22 16:09 xmnlab

I believe this was fixed by #20651, but this issue/ticket was never actually closed. Holler if this is still an issue in 3.x, and we can discuss!

rusackas avatar Feb 12 '24 20:02 rusackas