[
https://issues.apache.org/jira/browse/HBASE-7797?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13575060#comment-13575060
]
Enis Soztutar commented on HBASE-7797:
--------------------------------------
bq. In the above discussion it was acknowledged that HBase, being a top level
project, should have its own namespace.
True. HBase should be using o.a.hbase.
bq. Is a whole scale change across all files the only way of achieving that
goal ?
In this patch, I am not suggesting we migrate to o.a.hbase. The opposite.
I think we can revisit this decision while preparing for 1.0 or after trunk
becomes 2.0.
> Use consistent package name
> ---------------------------
>
> Key: HBASE-7797
> URL: https://issues.apache.org/jira/browse/HBASE-7797
> Project: HBase
> Issue Type: Bug
> Reporter: Enis Soztutar
> Assignee: Enis Soztutar
> Priority: Critical
> Fix For: 0.96.0
>
>
> This has been discussed here: http://search-hadoop.com/m/bXxiV1MGsYi2.
> We should not release 0.96 with two namespaces. This will cause further pain
> and confusion in the future (like log4j configuration, greping logs, etc).
> As much as I like it, I don't see us going o.a.hbase namespace, so let's move
> the Cell, and prefix tree classes to o.a.hadoop.hbase.
--
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
