You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Anoop Sam John (JIRA)" <ji...@apache.org> on 2016/10/04 11:32:20 UTC
[jira] [Commented] (HBASE-16758) Bring back
HBaseZeroCopyByteStringer stuff
[ https://issues.apache.org/jira/browse/HBASE-16758?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15545116#comment-15545116 ]
Anoop Sam John commented on HBASE-16758:
----------------------------------------
Checked and found in these classes, we might need HBaseZeroCopyByteStringer
FanOutOneBlockAsyncDFSOutputSaslHelper
BigDecimalColumnInterpreter
AccessControlUtil
AuthenticationTokenIdentifier
VisibilityClient
TokenUtil
VisibilityController
VisibilityUtils
> Bring back HBaseZeroCopyByteStringer stuff
> ------------------------------------------
>
> Key: HBASE-16758
> URL: https://issues.apache.org/jira/browse/HBASE-16758
> Project: HBase
> Issue Type: Sub-task
> Components: Protobufs
> Affects Versions: 2.0.0
> Reporter: Anoop Sam John
> Assignee: Anoop Sam John
> Fix For: 2.0.0
>
>
> After the shading and moving to 3.x PB, we dont need this. But many a places, we can not use the shaded classes. (Like FanOutOneBlockAsyncDFSOutputSaslHelper). In those places it will be better to go with old way of HBaseZeroCopyByteStringer fix to avoid copy.
> Need to see where all we need to do this.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)