fix: convert <NA> values to None instead of stringifying #22321
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
SUMMARY
With the pandas pyathena driver, we are seeing some issues with null values for integer columns. The bug is happening at this point where we get a type error
TypeError: Unserializable object <NA> of type <class 'pandas._libs.missing.NAType'>
and then we catch the error and try to stringify it, which resulted inpyarrow.lib.ArrowInvalid: Could not convert <NA> with type NAType: did not recognize Python value type when inferring an Arrow data type
For this fix, I am returning
None
for all pandas values so that the printed value looks like other nullable printed values.AFTER SCREENSHOTS OR ANIMATED GIF
TESTING INSTRUCTIONS
An athena db with the pyathena+pandas schema should be able to fetch values that are integer types with null values.
ADDITIONAL INFORMATION