hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-11891) Introduce HBaseInterfaceAudience level to denote class names that appear in configs.
Date Thu, 04 Sep 2014 09:12:51 GMT

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

Hadoop QA commented on HBASE-11891:
-----------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12666440/HBASE-11891.patch
  against trunk revision .
  ATTACHMENT ID: 12666440

    {color:green}+1 @author{color}.  The patch does not contain any @author tags.

    {color:green}+1 tests included{color}.  The patch appears to include 3 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/10710//console

This message is automatically generated.

> Introduce HBaseInterfaceAudience level to denote class names that appear in configs.
> ------------------------------------------------------------------------------------
>
>                 Key: HBASE-11891
>                 URL: https://issues.apache.org/jira/browse/HBASE-11891
>             Project: HBase
>          Issue Type: Improvement
>            Reporter: Sean Busbey
>            Assignee: Sean Busbey
>            Priority: Minor
>         Attachments: HBASE-11891.patch
>
>
> We have several classes that are private use as far as APIs are concerned, but the class
name appear in user provided config files.
> We should add an HBaseInterfaceAudience level CONFIG and use it to denote these classes
as LimitedPrivate.
> HBase contributors can then use this audience marking to see when changes to a FQCN will
require a release note to help upgrading users correct their configuration files.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message