-
Notifications
You must be signed in to change notification settings - Fork 14.5k
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
[SQL Lab] Saved Queries do not include parameters #20576
Comments
I have the same issue in 1.5.1. I was able to set parameters, after I saved the query I am not able to see saved parameters.. The only work around I figured is to save the parameters in description. copy params from description every time I run. Can someone please let me know If I miss any config to save params. Thanks! |
Same behaviour observed in Superset 2.0.0 I confirm that this same behaviour persists in 2.0.0. When I close the tab with the saved SQL query (together with the parameters), and reopen that, the parameters are gone, and I need to copy and paste my parameters again. I am not sure if it's meant to be like this, but It would be great that when the SQL template is saved in SQL Lab, the parameters are saved together as well. |
I still see this issue in v2.0.1. Looking at the merged PR I see that it was committed and then reverted. |
I figured an issue out:
FYI, I'm using superset 4.0.0 |
If a query with parameters is saved, the parameters are not stored with the query. So when executing a saved query, query fails without the necessary parameters.
How to reproduce the bug
Expected results
Saved Query should have the parameters.
Actual results
Saved Query does not have parameters.
Screenshots
If applicable, add screenshots to help explain your problem.
Environment
master
Dockerhub image
Checklist
Make sure to follow these steps before submitting your issue - thank you!
Additional context
In 'saved_query' table of metadata, there is column 'extra_json' which can/should be used to store the parameters.
The text was updated successfully, but these errors were encountered: