You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@arrow.apache.org by "Antoine Pitrou (Jira)" <ji...@apache.org> on 2021/02/24 14:28:00 UTC
[jira] [Updated] (ARROW-11748) [C++] Ensure Decimal128 and
Decimal256's fields are in native endian order
[ https://issues.apache.org/jira/browse/ARROW-11748?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Antoine Pitrou updated ARROW-11748:
-----------------------------------
Description:
Currently Decimal128 and Decimal256's fields are exclusively in littleendian order, which can yield surprising results when {{reinterpret_cast}}ing entries of a buffer to {{Decimal128*}} on a bigendian platform, see https://github.com/apache/arrow/pull/9554
These utility classes will be more useful if they are always usable from a buffer without swizzling.
was:
Currently Decimal128's fields are exclusively in littleendian order, which can yield surprising results when {{reinterpret_cast}}ing entries of a buffer to {{Decimal128*}} on a bigendian platform, see https://github.com/apache/arrow/pull/9554
These utility classes will be more useful if they are always usable from a buffer without swizzling
> [C++] Ensure Decimal128 and Decimal256's fields are in native endian order
> --------------------------------------------------------------------------
>
> Key: ARROW-11748
> URL: https://issues.apache.org/jira/browse/ARROW-11748
> Project: Apache Arrow
> Issue Type: Improvement
> Components: C++
> Affects Versions: 3.0.0
> Reporter: Ben Kietzman
> Priority: Major
>
> Currently Decimal128 and Decimal256's fields are exclusively in littleendian order, which can yield surprising results when {{reinterpret_cast}}ing entries of a buffer to {{Decimal128*}} on a bigendian platform, see https://github.com/apache/arrow/pull/9554
> These utility classes will be more useful if they are always usable from a buffer without swizzling.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)