superset
superset copied to clipboard
after upgrade superset 2.0 cant render a chart with event annotation on dashboard
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
If remove annotation chart render properly.
Expected: chart with event annotation worked as before.
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.
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.
hi everyone! just a friendly ping here to check if there is any update about this issue
Hello, any updates on this issue?
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.
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.
Ah you are right @joaocmd93 , I am seeing that behavior as well unfortunately.
Facing the same error here 😭
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.
This seems to be the fix https://github.com/apache/superset/pull/20651 We did a cherry pick and it fixes our dashboards.
nice!
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!