-
Notifications
You must be signed in to change notification settings - Fork 17
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
Datasets are empty in SQL Lab #537
Comments
Can you give a specific example of how to trigger this and what you see? There are some privacy and security considerations for granting access to data that we may have to think through or document more explicitly if non-superusers are working in SQL Lab. |
Right, I think those are explicitly set to not load the entire dataset if no filter is selected, otherwise the query will just time out anyway on a large dataset:
They could just temporarily change that to I don't know of a way to use the virtual datasets in SQL Lab, but I know there's a way to pass a filter value in the "..." menu -> Parameters and |
@Ian2012 is this still an issue we need to work more on, or were the suggestions sufficient? |
@bmtcril Yes, I can confirm we can close it now |
In the SQL Lab, there is no way to inject filters unless the use of raw SQL, and filter values are checked to be defined in many datasets so that the instructor dashboard makes sense.
This causes the SQL Lab and the create chart view obsolete as we can't previsualize, nor query the database there.
The solution would be to verify the current context (dashboard, chart, or sqllab) and provide a corresponding default values for the where clauses
The text was updated successfully, but these errors were encountered: