You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As a result, pyarrow falls back to parsing the number as float. But also here there are inherent limitations for what a float64 can represent, so it is expected that you cannot store such a number faithfully.
Given that other formats can represent larger ints (in my case ClickHouse supports 256-bit integers) and that other implementations support larger ints can this be turned into a feature request to add 128 and 256 bit integer support to this implementation?
Activity
asfimport commentedon Aug 16, 2022
Joris Van den Bossche / @jorisvandenbossche:
The integer number you have here is too large to fit in the int64 range:
So that means that this cannot be parsed in a pyarrow column of type int64. Explicitly asking for this would also give an error:
As a result, pyarrow falls back to parsing the number as float. But also here there are inherent limitations for what a float64 can represent, so it is expected that you cannot store such a number faithfully.
adriangb commentedon Nov 30, 2023
Given that other formats can represent larger ints (in my case ClickHouse supports 256-bit integers) and that other implementations support larger ints can this be turned into a feature request to add 128 and 256 bit integer support to this implementation?