[jira] [Commented] (SPARK-19008) Avoid boxing/unboxing overhead of calling a lambda with primitive type from Dataset program

["Kazuaki Ishizaki (JIRA)" <ji...@apache.org>]

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

Kazuaki Ishizaki commented on SPARK-19008:
------------------------------------------

I will work for this

> 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
>
> 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.4#6332)

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