You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Hyukjin Kwon (JIRA)" <ji...@apache.org> on 2019/05/21 04:33:42 UTC
[jira] [Resolved] (SPARK-12319) ExchangeCoordinatorSuite fails on
big-endian platforms
[ https://issues.apache.org/jira/browse/SPARK-12319?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hyukjin Kwon resolved SPARK-12319.
----------------------------------
Resolution: Incomplete
> ExchangeCoordinatorSuite fails on big-endian platforms
> ------------------------------------------------------
>
> Key: SPARK-12319
> URL: https://issues.apache.org/jira/browse/SPARK-12319
> Project: Spark
> Issue Type: Sub-task
> Components: SQL
> Affects Versions: 1.6.0
> Environment: Problems apparent on BE, LE could be impacted too
> Reporter: Adam Roberts
> Priority: Minor
> Labels: big-endian, bulk-closed
>
> JIRA to cover endian specific problems - since testing 1.6 I've noticed problems with DataFrames on BE platforms, e.g. https://issues.apache.org/jira/browse/SPARK-9858
> [~joshrosen] [~yhuai]
> Current progress: using com.google.common.io.LittleEndianDataInputStream and com.google.common.io.LittleEndianDataOutputStream within UnsafeRowSerializer fixes three test failures in ExchangeCoordinatorSuite but I'm concerned around performance/wider functional implications
> "org.apache.spark.sql.DatasetAggregatorSuite.typed aggregation: class input with reordering" fails as we expect "one, 1" but instead get "one, 9" - we believe the issue lies within BitSetMethods.java, specifically around: return (wi << 6) + subIndex + java.lang.Long.numberOfTrailingZeros(word);
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org