You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Wenchen Fan (JIRA)" <ji...@apache.org> on 2017/03/10 07:00:12 UTC
[jira] [Resolved] (SPARK-19008) Avoid boxing/unboxing overhead of
calling a lambda with primitive type from Dataset program
[ https://issues.apache.org/jira/browse/SPARK-19008?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Wenchen Fan resolved SPARK-19008.
---------------------------------
Resolution: Fixed
Fix Version/s: 2.2.0
Issue resolved by pull request 17172
[https://github.com/apache/spark/pull/17172]
> Avoid boxing/unboxing overhead of calling a lambda with primitive type from Dataset program
> -------------------------------------------------------------------------------------------
>
> Key: SPARK-19008
> URL: https://issues.apache.org/jira/browse/SPARK-19008
> Project: Spark
> Issue Type: Improvement
> Components: SQL
> Reporter: Kazuaki Ishizaki
> Fix For: 2.2.0
>
>
> In a [discussion|https://github.com/apache/spark/pull/16391#discussion_r93788919] between [~cloud_fan] and [~kiszk], we noticed an opportunity to avoid boxing/unboxing overhead when a Dataset program calls a lambda, which operates on a primitive type, written in Scala.
> In such a case, Catalyst can directly call a method {{<primitiveType> apply(<primitiveType>);}} instead of {{Object apply(Object);}}.
> Of course, the best solution seems to be [here|https://issues.apache.org/jira/browse/SPARK-14083].
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org