You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Apache Spark (Jira)" <ji...@apache.org> on 2020/09/21 08:57:00 UTC
[jira] [Commented] (SPARK-32950) No need for some big-endian
specific code paths in {On,Off}HeapColumnVector
[ https://issues.apache.org/jira/browse/SPARK-32950?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17199264#comment-17199264 ]
Apache Spark commented on SPARK-32950:
--------------------------------------
User 'mundaym' has created a pull request for this issue:
https://github.com/apache/spark/pull/29815
> No need for some big-endian specific code paths in {On,Off}HeapColumnVector
> ---------------------------------------------------------------------------
>
> Key: SPARK-32950
> URL: https://issues.apache.org/jira/browse/SPARK-32950
> Project: Spark
> Issue Type: Improvement
> Components: SQL
> Affects Versions: 3.0.1
> Reporter: Michael Munday
> Priority: Trivial
> Labels: big-endian
>
> There is no need for a separate code path for big-endian platforms in putFloats and putDoubles in OnHeapColumnVector and OffHeapColumnVector. Since SPARK-26985 was fixed the values have been copied in native byte order so the code required to perform this operation can be the same on both little- and big-endian platforms.
--
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