Skip to content
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

Add column name to exception "Unsupported Pyarrow type" in athena_types_from_pandas/pyarrow2athena #639

Closed
nmduarteus opened this issue Apr 6, 2021 · 1 comment · Fixed by #646
Assignees
Labels
enhancement New feature or request minor release Will be addressed in the next minor release ready to release
Milestone

Comments

@nmduarteus
Copy link

Is your idea related to a problem? Please describe.
While trying to convert pandas to athena types if Unsupported Pyarrow type is raised, there is no way of knowing what column is causing the exception.
While for exceptions.UndetectedType the column name is displayed, the same does not happen for Unsupported Pyarrow type.

Exception example:
'Unsupported Pyarrow type: time64[us]'

Describe the solution you'd like
It would be nice to have the name of the column that is causing the exception just like happens to the UndetectedType exception.

Exception example:
'Column abc - Unsupported Pyarrow type: time64[us]'

@nmduarteus nmduarteus added the enhancement New feature or request label Apr 6, 2021
@jaidisido jaidisido added this to the 2.7.0 milestone Apr 12, 2021
@jaidisido jaidisido added minor release Will be addressed in the next minor release ready to release labels Apr 12, 2021
@jaidisido jaidisido linked a pull request Apr 12, 2021 that will close this issue
@jaidisido jaidisido self-assigned this Apr 15, 2021
@jaidisido
Copy link
Contributor

Covered in 2.7.0 release

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request minor release Will be addressed in the next minor release ready to release
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants