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

Hudson commented on HBASE-16758:
--------------------------------

SUCCESS: Integrated in Jenkins build HBase-Trunk_matrix #1730 (See 
[https://builds.apache.org/job/HBase-Trunk_matrix/1730/])
HBASE-16758  back HBaseZeroCopyByteStringer stuff. (anoopsamjohn: rev 
617dfe18cdc287ea5886e5a9567c9abcd6c0fa28)
* (edit) 
hbase-client/src/main/java/org/apache/hadoop/hbase/security/visibility/VisibilityClient.java
* (edit) 
hbase-server/src/main/java/org/apache/hadoop/hbase/io/asyncfs/FanOutOneBlockAsyncDFSOutputSaslHelper.java
* (edit) 
hbase-server/src/main/java/org/apache/hadoop/hbase/security/visibility/VisibilityUtils.java
* (edit) 
hbase-client/src/main/java/org/apache/hadoop/hbase/client/coprocessor/BigDecimalColumnInterpreter.java
* (edit) 
hbase-client/src/main/java/org/apache/hadoop/hbase/security/access/AccessControlUtil.java
* (edit) 
hbase-server/src/main/java/org/apache/hadoop/hbase/security/visibility/VisibilityController.java
* (edit) 
hbase-server/src/main/java/org/apache/hadoop/hbase/security/token/TokenUtil.java


> 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
>
>         Attachments: HBASE-16758.patch
>
>
> 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)

Reply via email to