-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
panic reading AWS-generated parquet file #2963
Labels
bug
Something isn't working
Comments
Can be triggered just be selecting that column, and also if only running a select against one of the parquet files rather than all 3.
|
perhaps related to #2910 |
Yes! I checked out your branch and built, these queries work with your patch. Can you update your PR to close this issue as well? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
A clear and concise description of what the bug is.
Given some AWS Costs parquet files (parquet files generated by AWS cost and usage reporting), a query executed against those files results in a panic:
From datafusion-cli, using latest master as of the time of this bug report:
It seems to be this line_item_resource_id field in particular, as I was able to group by other fields without issue.
To Reproduce
Steps to reproduce the behavior:
I don't think I should upload our AWS costs files for general consumption, so I'm open to suggestions how to recreate a test case.
Expected behavior
A clear and concise description of what you expected to happen.
not panic :)
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: