[
https://issues.apache.org/jira/browse/HBASE-10431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13885792#comment-13885792
]
Hadoop QA commented on HBASE-10431:
-----------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12625957/HBASE-10431.v3-0.98.patch
against trunk revision .
ATTACHMENT ID: 12625957
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 18 new
or modified tests.
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/8554//console
This message is automatically generated.
> Rename com.google.protobuf.ZeroCopyLiteralByteString
> ----------------------------------------------------
>
> Key: HBASE-10431
> URL: https://issues.apache.org/jira/browse/HBASE-10431
> Project: HBase
> Issue Type: Bug
> Affects Versions: 0.96.1.1
> Reporter: Nicolas Liochon
> Assignee: Nicolas Liochon
> Fix For: 0.98.0, 0.96.2, 0.99.0
>
> Attachments: HBASE-10431.patch, HBASE-10431.v2.patch,
> HBASE-10431.v3-0.96.patch, HBASE-10431.v3-0.98.patch, HBASE-10431.v3.patch
>
>
> As we are hijacking the protobuf package, we should do our best to limit the
> probability to have a conflict on the class name.
> Today, we have the same class name as AsyncHBase, but our contains a method
> that AsyncHBase does not have.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
