[
https://issues.apache.org/jira/browse/HBASE-9579?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13772520#comment-13772520
]
Hadoop QA commented on HBASE-9579:
----------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12604141/hbase-9579.v2.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+0 tests included{color}. The patch appears to be a
documentation patch that doesn't require tests.
{color:green}+1 hadoop1.0{color}. The patch compiles against the hadoop
1.0 profile.
{color:red}-1 hadoop2.0{color}. The patch failed to compile against the
hadoop 2.0 profile.
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/7309//console
This message is automatically generated.
> Sanity check visiblity and audience for server-side modules.
> ------------------------------------------------------------
>
> Key: HBASE-9579
> URL: https://issues.apache.org/jira/browse/HBASE-9579
> Project: HBase
> Issue Type: Bug
> Components: documentation
> Affects Versions: 0.95.2
> Reporter: Jonathan Hsieh
> Assignee: Jonathan Hsieh
> Attachments: hbase-9579.patch, hbase-9579.v2.patch
>
>
> Similar to HBASE-9495 we should audit the hbase-hadoop*-compat,
> hbase-prefix-tree, hbase-protocol and hbase server-modules.
> I'll go through each module first making most things private, and then do a
> second pass using some sort of LimitedPrivate marking for apis that we'd
> expect coprocs or advanced tests to use.
> This is less urgent that the work for the client facing apis.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
