[
https://issues.apache.org/jira/browse/HBASE-9579?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13772408#comment-13772408
]
Nick Dimiduk commented on HBASE-9579:
-------------------------------------
bq. Should I make all the o.a.h.h.mapred public then?
Yes, thanks.
bq. Sounds like for rest I should make them private or limitedpublic(rest)?
They will show up in the dev api java docs.
My desire is for the REST package-info docs to be included in user-facing
documentation. This is the most complete documentation for the REST gateway
public syntax.
> 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
