-
Notifications
You must be signed in to change notification settings - Fork 14.6k
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
KeyError when using uppercase Metrics with Athena (in Superset 1.0.1) #13481
Comments
@mrshu thanks for reporting! we may not get to any data-specific issues soon. If you have a solution in-place, feel free to ope n a PR. We will make sure it get reviewed. 🙏 |
Thank you @junlincc! Sadly, the only solution that worked for us was manually renaming the Metric in question. I find this strange, as the superset/superset/db_engine_specs/athena.py Lines 58 to 66 in c91c455
If you could provide any pointers, I would be happy to put a PR together! |
Sounds like this can be closed. Thanks all! |
After updating to Superset 1.0.1 we started running into an issue with the Athena adapter, where Metrics with uppercase name would stop working with the following error:
Strangely enough, we found out that this issue does not persist when the name of metric gets lowercased. It therefore seems like the following issues/PRs may be related:
Expected results
The computation of the defined metric.
Actual results
An error:
The stacktrace is as follows:
Screenshots
Here is what the chart rendering looks like:

And this is what one can find in the Dataset editor (Metrics tab):

How to reproduce the bug
New_metric
New_metric
as the metric to be used in itEnvironment
Checklist
Make sure to follow these steps before submitting your issue - thank you!
The text was updated successfully, but these errors were encountered: