-
Notifications
You must be signed in to change notification settings - Fork 13.7k
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
Creation of a dimension using SQL Server data warehouse fails with 'no field of name' #23848
Comments
A simple way to reproduce this is to run this query in SQL Lab:
|
I can also confirm we have seen the same thing when upgrading from 2.0.1 to 2.1.0. A workaround we have is to use calculated columns at the dataset level until patched. |
Would be nice to see this fixed. |
I hope this issue will be fixed soon |
Tempted to close this as stale... but is anyone able to confirm if this is still an issue in 3.x? |
I can confirm it's still a bug in 4.0.0rc1. |
This persists in 4.0.2. It also just hit me when a new alert failed to fire because I had set the condition |
In Superset 2.1.0 when I try to create a dimension variable based on a column, it fails with "no field of name". Logs and screenshot below. Likely related to #23213.
How to reproduce the bug
Expected results
This should succeed. I am confident this worked in 2.0.1, I just noticed the chart broken on the dashboard under 2.1.0. But I have not fired up an old 2.0.1 instance to confirm 100% that it's a regression.
Actual results
SQL Query sent to my database:
SELECT TOP 1 DATEPART(year, date_completed) FROM dbo.[myTable]
This is valid SQL Server and returns a variable with
(No column name)
, which is causing the error.Superset logs
Environment
(please complete the following information):
The text was updated successfully, but these errors were encountered: