Is there a reason why the prefix-tree and cell code is inside
org.apache.hbase instead of the traditional org.apache.hadoop.hbase?

On Wed, Feb 6, 2013 at 11:46 PM, Matteo Bertozzi <
[EMAIL PROTECTED]> wrote:

> Is there a reason why the prefix-tree and cell code is inside
> org.apache.hbase instead of the traditional org.apache.hadoop.hbase?
>
Our code should be homed at o.a.hbase rather than at o.a.hadoop.hbase given
we are a top-level apache project.  We were once part of hadoop so it made
sense then being at o.a.hadoop.hbase.

Moving all to o.a.hbase would have been an incompatible change especially
by the time it made it out to the API.  It would also have been a mountain
of work.  Making the change was never of high enough priority.

Rather than do the big bang move, thought was that new baseline code could
come in at o.a.hbase and we'd migrate slowly to the new root.

I suppose I should have put this up on dev list for folks to throw darts at?
St.Ack

Related question, any reason (other than lack of inertia) why we are
still org.apache.hadoop.hbase instead of org.apache.hbase?

Jon.

On Wed, Feb 6, 2013 at 11:46 PM, Matteo Bertozzi
<[EMAIL PROTECTED]> wrote:
> Is there a reason why the prefix-tree and cell code is inside
> org.apache.hbase instead of the traditional org.apache.hadoop.hbase?

--
// Jonathan Hsieh (shay)
// Software Engineer, Cloudera
// [EMAIL PROTECTED]

There have been previous discussions about changing.  I don't recall the
exact conclusions, but if we did change we would break every java client
there.  Is the benefit really worth the mass incompatibility?
On Thu, Feb 7, 2013 at 9:10 AM, Jonathan Hsieh <[EMAIL PROTECTED]> wrote:

> Related question, any reason (other than lack of inertia) why we are
> still org.apache.hadoop.hbase instead of org.apache.hbase?
>
> Jon.
>
> On Wed, Feb 6, 2013 at 11:46 PM, Matteo Bertozzi
> <[EMAIL PROTECTED]> wrote:
> > Is there a reason why the prefix-tree and cell code is inside
> > org.apache.hbase instead of the traditional org.apache.hadoop.hbase?
>
>
>
> --
> // Jonathan Hsieh (shay)
> // Software Engineer, Cloudera
> // [EMAIL PROTECTED]
>

I'ev filed https://issues.apache.org/jira/browse/HBASE-7797 for this. We
should not release with two namespaces.
On Thu, Feb 7, 2013 at 9:37 AM, Gary Helmling <[EMAIL PROTECTED]> wrote:

> There have been previous discussions about changing.  I don't recall the
> exact conclusions, but if we did change we would break every java client
> there.  Is the benefit really worth the mass incompatibility?
>
>
> On Thu, Feb 7, 2013 at 9:10 AM, Jonathan Hsieh <[EMAIL PROTECTED]> wrote:
>
> > Related question, any reason (other than lack of inertia) why we are
> > still org.apache.hadoop.hbase instead of org.apache.hbase?
> >
> > Jon.
> >
> > On Wed, Feb 6, 2013 at 11:46 PM, Matteo Bertozzi
> > <[EMAIL PROTECTED]> wrote:
> > > Is there a reason why the prefix-tree and cell code is inside
> > > org.apache.hbase instead of the traditional org.apache.hadoop.hbase?
> >
> >
> >
> > --
> > // Jonathan Hsieh (shay)
> > // Software Engineer, Cloudera
> > // [EMAIL PROTECTED]
> >
>

I just started putting it there a year ago because i thought we were trying
to move out of the hadoop package after becoming a top level project.
 Seems like there hasn't been much of a push though.  Easy enough to move
prefix-tree back into hadoop if we want.

Some issues in the way of moving everything out of hadoop:
* @InterfaceAudience.Public annotations on RPC classes
* classes used by client code (Bytes.java) would have their imports broken
* HFiles contain full package name of their comparators
On Thu, Feb 7, 2013 at 9:10 AM, Jonathan Hsieh <[EMAIL PROTECTED]> wrote:

> Related question, any reason (other than lack of inertia) why we are
> still org.apache.hadoop.hbase instead of org.apache.hbase?
>
> Jon.
>
> On Wed, Feb 6, 2013 at 11:46 PM, Matteo Bertozzi
> <[EMAIL PROTECTED]> wrote:
> > Is there a reason why the prefix-tree and cell code is inside
> > org.apache.hbase instead of the traditional org.apache.hadoop.hbase?
>
>
>
> --
> // Jonathan Hsieh (shay)
> // Software Engineer, Cloudera
> // [EMAIL PROTECTED]
>