Closed mmcdermott closed 3 weeks ago
Right, our AnyValue
cast doesn't do the same as our cast
in our arrow
kernels. This should be fixed.
I'd be happy to take a look.
@ritchie46 I have fixed this issue where the extraction literal floats is cast to an integer and then to a string. I now have it where it is determine right datatype then extraction float or integer then cast to string.
However, if you want the AnyValue
version of cast
to work like the arrow
version of cast
this will take some time to test. Do you want this rewrite cast to be similar or create PR with the simple fix of the above issue?
Question should the Boolean literal be 0
and 1
or true
and false
?
Checks
Reproducible example
Another example, from 1.2.1, which also highlights that the issue is unique to literals.
Log output
No response
Issue description
When I make a literal of a floating point value then cast it to a string, the value is rounded down to the nearest integer.
Expected behavior
I expect the string version of the float to retain the decimal points, much like python's
str
function does.Installed versions