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

read decimal data type from parquet file with binary physical type #2159

Closed
liukun4515 opened this issue Jul 25, 2022 · 0 comments · Fixed by #2160
Closed

read decimal data type from parquet file with binary physical type #2159

liukun4515 opened this issue Jul 25, 2022 · 0 comments · Fixed by #2160
Labels
enhancement Any new improvement worthy of a entry in the changelog parquet Changes to the parquet crate

Comments

@liukun4515
Copy link
Contributor

Is your feature request related to a problem or challenge? Please describe what you are trying to do.

From the definition of parquet spec format: https://github.com/apache/parquet-format/blob/master/src/main/thrift/parquet.thrift#L245

The decimal logical type can't be stored as int32,int64,fixed binary, and binary.

In the current arrow-parquet, we can't convert binary parquet data to decimal arrow data.

This is just compatible implementation for decimal in parquet.

Describe the solution you'd like
A clear and concise description of what you want to happen.

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

Additional context
Add any other context or screenshots about the feature request here.

@liukun4515 liukun4515 added the enhancement Any new improvement worthy of a entry in the changelog label Jul 25, 2022
@alamb alamb added the parquet Changes to the parquet crate label Aug 4, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement Any new improvement worthy of a entry in the changelog parquet Changes to the parquet crate
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants