hadoop-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Todd Lipcon <t...@cloudera.com>
Subject Re: LimitedPrivate and HBase
Date Mon, 06 Jun 2011 17:00:47 GMT
On Mon, Jun 6, 2011 at 9:45 AM, Allen Wittenauer <aw@apache.org> wrote:

>        I have some concerns over the recent usage of LimitedPrivate being
> opened up to HBase.  Shouldn't HBase really be sticking to public APIs
> rather than poking through some holes?  If HBase needs an API, wouldn't
> other clients as well?

IMO LimitedPrivate can be used to open an API for a specific project when
it's not clear that the API is generally useful, and/or we anticipate the
API might be pretty unstable. Marking it LimitedPrivate to HBase gives us
the opportunity to talk to the HBase team and say "hey, we want to rename
this without @Deprecation" or "hey, we're going to kill this, is that OK?"
Making it true public, even if we call it Unstable, is a bit harder to move.

I agree that most of these things in the long run would be determined
generally useful and made public.

Do you have a specific thing in mind?

Todd Lipcon
Software Engineer, Cloudera

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message