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
Azure SQL - SQL Lab Query Error #3075
Comments
I think the issue here is that sql_lab.get_sql_results should raise again the exception after doing the cleanup so that the callers can handle the failure too. Then i have no clue for the pandas exception though. |
As caller expect it to raise an exception instead of returning None. Refs apache#3075
As caller expect it to raise an exception instead of returning None. Refs #3075
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. For admin, please label this issue |
Make sure these boxes are checked before submitting your issue - thank you!
Superset version
mssql+pyodbc==4.0.17
Database is Azure hosted database
Expected results
When executing a query in the SQL Editor against a successfully added table, I expect to see the results of the query and no error.
Actual results
HTML formatted stacktrace appears in the results tab below the query editor when selecting from
dbo.CashOperations
.HTML formatted error appears in the results tab below the query editor when selecting from
CashOperations
.Full stacktrace from server when executing the
dbo.CashOperations
query.Steps to reproduce
I found a thread referencing this issue on a Google group here however it seemed to reference an earlier version of Superset (
0.17.5
). The responder mentionss "for Azure we currently don't have an entry for it in the docs as and in the moduledb_engine_specs.py
where we specify specific logic or configuration that Superset requires" however there is aMssqlEngineSpec(BaseEngineSpec)
class.Curious if this is indication there is no support of if this is an issue. It should be noted I can create visualization slices with no errors using the same datasource.
The text was updated successfully, but these errors were encountered: