You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Dongjoon Hyun (Jira)" <ji...@apache.org> on 2020/07/28 17:38:00 UTC
[jira] [Resolved] (SPARK-32458) Mismatched row access sizes in
tests
[ https://issues.apache.org/jira/browse/SPARK-32458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dongjoon Hyun resolved SPARK-32458.
-----------------------------------
Fix Version/s: 3.1.0
Resolution: Fixed
Issue resolved by pull request 29258
[https://github.com/apache/spark/pull/29258]
> Mismatched row access sizes in tests
> ------------------------------------
>
> Key: SPARK-32458
> URL: https://issues.apache.org/jira/browse/SPARK-32458
> Project: Spark
> Issue Type: Bug
> Components: SQL
> Affects Versions: 3.0.0
> Reporter: Michael Munday
> Assignee: Michael Munday
> Priority: Minor
> Labels: catalyst, endianness
> Fix For: 3.1.0
>
>
> The RowEncoderSuite and UnsafeMapSuite tests fail on big-endian systems. This is because the test data is written into the row using unsafe operations with one size and then read back using a different size. For example, in UnsafeMapSuite the test data is written using putLong and then read back using getInt. This happens to work on little-endian systems but these differences appear to be typos and cause the tests to fail on big-endian systems.
> I have a patch that fixes the issue.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org