hbase-issues mailing list archives

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

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

Weiqing Yang updated HBASE-16818:
---------------------------------
    Description: 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.  (was: 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.)

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