hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Hsieh (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HBASE-9579) Sanity check visiblity and audience for server-side modules.
Date Thu, 19 Sep 2013 00:14:52 GMT

     [ https://issues.apache.org/jira/browse/HBASE-9579?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Jonathan Hsieh updated HBASE-9579:
----------------------------------

    Description: 
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.

  was:
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.

    
> 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
>
> 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

Mime
View raw message