[jira] [Resolved] (SPARK-51093) Fix minor endianness issues in tests

["Max Gekk (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/SPARK-51093?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Max Gekk resolved SPARK-51093.
------------------------------
    Fix Version/s: 4.0.0
       Resolution: Fixed

Issue resolved by pull request 49812
[https://github.com/apache/spark/pull/49812]

> Fix minor endianness issues in tests
> ------------------------------------
>
>                 Key: SPARK-51093
>                 URL: https://issues.apache.org/jira/browse/SPARK-51093
>             Project: Spark
>          Issue Type: Bug
>          Components: SQL
>    Affects Versions: 4.0.0, 3.5.4, 3.5.5, 4.1.0
>            Reporter: Jonathan Albrecht
>            Assignee: Jonathan Albrecht
>            Priority: Minor
>              Labels: big-endian, pull-request-available
>             Fix For: 4.0.0
>
>
> There are a few minor endianness related issues in tests that I encountered while building spark on s390x:
> ArrayBasedMapBuilderSuite: The output of the UnsafeRow.toString() is based on the underlying bytes and is endian dependent.
> WriteDistributionAndOrderingSuite: Casting the id of type Int to Long doesn't work on big endian platforms because the BucketFunction calls UnsafeRow.getLong() for that column. That happens to work on little endian since an int field is stored in the first 4 bytes of the 8 byte field so positive ints are layed out the same as positive longs ie. little endian order. On big endian, the layout of UnsafeRow int fields does not happen to match the layout of long fields for the same number.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org