-
Notifications
You must be signed in to change notification settings - Fork 16.5k
fix: nan is not properly handled for Athena connections [sc-89372] #37071
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
base: master
Are you sure you want to change the base?
Conversation
|
CodeAnt AI is reviewing your PR. Thanks for using CodeAnt! 🎉We're free for open-source projects. if you're enjoying it, help us grow by sharing. Share on X · |
Code Review Agent Run #1c6679Actionable Suggestions - 0Review Details
Bito Usage GuideCommands Type the following command in the pull request comment and save the comment.
Refer to the documentation for additional commands. Configuration This repository uses Documentation & Help |
Nitpicks 🔍
|
✅ Deploy Preview for superset-docs-preview ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
|
CodeAnt AI finished reviewing your PR. |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #37071 +/- ##
===========================================
+ Coverage 0 67.86% +67.86%
===========================================
Files 0 642 +642
Lines 0 47989 +47989
Branches 0 5248 +5248
===========================================
+ Hits 0 32568 +32568
- Misses 0 14138 +14138
- Partials 0 1283 +1283
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
Summary
Fix NaN Handling in DataFrame Conversion for All Database Connections
Problem Description
When executing queries that produce NaN (Not a Number) values—such as division by zero operations—Superset would fail when attempting to save the results as a dataset or serialize the data to JSON. This issue affected all database connections, but was particularly noticeable with Amazon Athena, where queries like
SELECT 0.00 / 0.00return IEEE 754 NaN values.The root cause was that Python's
float('nan')values cannot be serialized to valid JSON without special handling. When users attempted to save query results containing NaN values as datasets, the JSON serialization would fail, resulting in errors displayed in the UI.ADDITIONAL INFORMATION