You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@arrow.apache.org by "Ian Cook (Jira)" <ji...@apache.org> on 2021/02/01 15:15:00 UTC

[jira] [Created] (ARROW-11455) [R] Improve handling of -2^31 in 32-bit integer fields

Ian Cook created ARROW-11455:
--------------------------------

             Summary: [R] Improve handling of -2^31 in 32-bit integer fields
                 Key: ARROW-11455
                 URL: https://issues.apache.org/jira/browse/ARROW-11455
             Project: Apache Arrow
          Issue Type: Improvement
          Components: R
    Affects Versions: 3.0.0
            Reporter: Ian Cook
            Assignee: Ian Cook


R’s {{integer}} range is 1 smaller than the normal 32-bit integer range of C++, Java, etc. In R, it’s {{-2^31 + 1}} to {{2^31 - 1}}. Elsewhere, it’s {{-2^31}} to {{2^31 - 1}}. So R's native {{integer}} type cannot represent {{-2^31}} ({{-2147483648}}).

If you run {{-2147483648L}} in R, it converts it to {{numeric}} and issues a warning:
{code:java}
Warning message:
non-integer value 2147483648L qualified with L; using numeric value 
{code}
In the {{arrow}} R package, when a 32-bit integer Arrow field containing the value {{-2147483648}} is converted to an R {{integer}} vector, the value is silently converted to {{NA_integer_}}. Consider whether we should handle this case differently and whether it is feasible to do so without performance regressions. Other possible behaviors might be:
 * Converting the value to {{NA_integer_}} with a warning
 * Converting the field to {{bit64::integer64}} with a warning
 * Converting the field to {{base::numeric}} with a warning
 * Allowing the user to specify an argument or option to control the behavior



--
This message was sent by Atlassian Jira
(v8.3.4#803005)