hbase-issues mailing list archives

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

     [ https://issues.apache.org/jira/browse/HBASE-16818?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Ted Yu updated HBASE-16818:
---------------------------
       Resolution: Fixed
     Hadoop Flags: Reviewed
    Fix Version/s: 2.0.0
           Status: Resolved  (was: Patch Available)

Thanks for the patch, Weiqing

> 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