You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am experiencing an issue with Apache Superset, specifically within the SQL Lab section. When accessing SQLLab via a URL without the sql parameter, the standalone mode is successfully applied, and the interface adjusts accordingly, hiding unnecessary UI elements. Here is an example of such a URL:
I would appreciate any insights or suggestions on how to ensure that the standalone mode is applied consistently, regardless of whether the SQL parameter is included or not.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hello,
I am experiencing an issue with Apache Superset, specifically within the SQL Lab section. When accessing SQLLab via a URL without the sql parameter, the standalone mode is successfully applied, and the interface adjusts accordingly, hiding unnecessary UI elements. Here is an example of such a URL:
http://myweburl/superset/sqllab/?standalone=true&dbid=1&name=test
However, when I include an sql parameter in the URL, the standalone mode does not seem to work. An example of this problematic URL is:
http://myweburl/superset/sqllab/?standalone=true&dbid=1&name=test&sql=select%20*%20from%20mydb
I would appreciate any insights or suggestions on how to ensure that the standalone mode is applied consistently, regardless of whether the SQL parameter is included or not.
Thank you for your help!
Beta Was this translation helpful? Give feedback.
All reactions