Reading/writing Dec128
- Dominant language
- Julia
- Stars
- 312
- Forks
- 78
- PR merge metrics
- No merged PRs in 30d
Description
Hi,
Noticed some odd behaviour with reading/writing Dec128 data types. Just documenting in case this is an issue (and not me making a mistake).
I have some data (from SQL) in Dec128 format, which I write into an arrow table with:
Arrow.write("file.arrow", df)
When re-read with df2 = Arrow.Table("file.arrow") |> DataFrame(_)
The data is read as float64 and scrambled.
And reading https://arrow.apache.org/docs/python/api/datatypes.html , I thought that Arrow is trying to support Dec128 types.
Hope you find that helpful.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with the Arrow.write("file.arrow", df) and Arrow.Table("file.arrow") entry points shown in the report, then reproduce the Dec128 round trip described. Done means Dec128 values are read back with the correct type and values instead of becoming scrambled float64 data.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- julia
- Domain
- data
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100