hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-16818) Avoid multiple copies of binary data during the conversion from Result to Row
Date Fri, 14 Oct 2016 19:52:22 GMT

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

Hudson commented on HBASE-16818:
--------------------------------

FAILURE: Integrated in Jenkins build HBase-Trunk_matrix #1786 (See [https://builds.apache.org/job/HBase-Trunk_matrix/1786/])
HBASE-16818 Avoid multiple copies of binary data during the conversion (tedyu: rev a68c0e2a34186e2f9e8725d7c5b2cb5c88bab148)
* (edit) hbase-spark/src/main/scala/org/apache/hadoop/hbase/spark/DefaultSource.scala


> Avoid multiple copies of binary data during the conversion from Result to Row
> -----------------------------------------------------------------------------
>
>                 Key: HBASE-16818
>                 URL: https://issues.apache.org/jira/browse/HBASE-16818
>             Project: HBase
>          Issue Type: Improvement
>          Components: spark
>            Reporter: Weiqing Yang
>            Assignee: Weiqing Yang
>             Fix For: 2.0.0
>
>         Attachments: HBASE-16818_v0.patch
>
>
> In the buildRow() of HBaseRelation, CellUtil.cloneValue will already create a copy of
the data. If the data type is BinaryType, another copy is being made within Utils.hbaseFieldToScalaType
in Utils.scala. Generally, binary data can be fairly large, so copying may be an expensive
operation.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message