[jira] [Commented] (SPARK-12319) Address endian specific problems surfaced in 1.6

["Sean Owen (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/SPARK-12319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15055985#comment-15055985 ] 

Sean Owen commented on SPARK-12319:
-----------------------------------

Do you have any more detail here -- what specifically is the test failure and fix?
You're referring to bit twiddling ops in BitSetMethods, but these operators don't have an endian-ness.

> Address endian specific problems surfaced in 1.6
> ------------------------------------------------
>
>                 Key: SPARK-12319
>                 URL: https://issues.apache.org/jira/browse/SPARK-12319
>             Project: Spark
>          Issue Type: Bug
>          Components: SQL
>    Affects Versions: 1.6.0
>         Environment: BE platforms
>            Reporter: Adam Roberts
>            Priority: Critical
>
> 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
(v6.3.4#6332)

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