-
Notifications
You must be signed in to change notification settings - Fork 13.9k
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
Error importing dashboard #27027
Comments
Nice issue description @ruifpedro! Thank you. I'll tag some folks with more knowledge about that feature: @betodealmeida @eschutho @rusackas |
Hello @ruifpedro thank you for detailed explanation. It helped us as well. |
Hello @ruifpedro , Your detailed explanation helped us figure out that checking the "enable row expansion" is causing the dashboard import error in the same instance and different instance, we fixed it by writing code to stop schema options keys from going into the export zip. |
@ruifpedro do you manage to solve the issue?i get the same issue how can i fix it? |
I've missed your comment! Yes that it's the case, I'm also unable to uncheck the "enable row expansion" option. |
As my first post states, I've managed to circumvent the problem by simply, exporting the dashboard, opening up the zip and modifying the respective database yaml to manually remove the |
Hey guys ! It's still an issue on 4.0.2; is a fix planned for it ? |
Welcomed, yes, but planned... not so much. Unless @yousoph is aware of this and planning to get it in a Preset sprint, I doubt we'll see a fix soon. Contributions/PRs more than welcomed if you'd like to tackle this one! |
Bug description
Hey Superset team!
Since I've upgraded from Superset v3.0.0 to v3.1.0, I have stopped being able to successfully import dashboards that contain datasets that specifically use a Trino datasource, with the new feature of
Enable row expansion in schemas
enabled.Additionally figured out that if I modify the respective database yaml that is shipped out in the zip export, and manually remove the
extra.schema_options
key and values, importing works. This mitigates the problem for the time being, but does not solve it.The source of the problem seems to lie in the Superset importing tool not take into account this new Trino feature.
I will provide evidence and more context below.
Looking forward for your response and happy to clarify any more details.
How to reproduce the bug
Enable row expansion in schemas
enabledScreenshots/recordings
Superset stacktrace:
Screenshots
Superset error
Browser debug
Trino Database connection
Trino Database exported YAML
Superset version
3.1.0
Python version
3.9
Node version
Not applicable
Browser
Firefox
Additional context
I have the following feature flags enabled:
There are no customization made on Superset, but the container image is packaged by me in order to include necessary dependencies like the Trino connector.
The Superset is deployed in Kubernetes using the official Superset helm chart.
About the data source I am querying, I've already provided details on it on the post.
Checklist
The text was updated successfully, but these errors were encountered: