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 2016/03/14 19:24:33 UTC

[jira] [Commented] (SPARK-13661) Avoid the copy of UnsafeRow in HashedRelation

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

Apache Spark commented on SPARK-13661:
--------------------------------------

User 'davies' has created a pull request for this issue:
https://github.com/apache/spark/pull/11666

> Avoid the copy of UnsafeRow in HashedRelation
> ---------------------------------------------
>
>                 Key: SPARK-13661
>                 URL: https://issues.apache.org/jira/browse/SPARK-13661
>             Project: Spark
>          Issue Type: Improvement
>          Components: SQL
>            Reporter: Davies Liu
>
> We usually build the HashedRelation on top of array of UnsafeRow, the copy could be avoided.
> The caller of HashedRelation need to do the copy if it's needed.
> Another approach could be making the copy() of UnsafeRow smart so that it know when should copy the bytes or not, this could be also useful for other components. 



--
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