[ 
https://issues.apache.org/jira/browse/HBASE-7797?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13575622#comment-13575622
 ] 

Enis Soztutar commented on HBASE-7797:
--------------------------------------

I can see the intention, but Cell is a small part of the overall client API. Is 
there a plan to gradually move the other parts of the API to the new namespace, 
or rewrite v2 APIs? If not, then we might as well end up with 2 namespaces for 
years, which I am trying to avoid. This looks like the mapred vs mapreduce set 
of APIs, but the difference is that mapreduce mostly replaces the whole mapred 
namespace, whereas Cell is not. 
Having said that, if we plan to migrate filters, coprocessors, htable, etc for 
the new Cell interface and keep the BC versions in place we might as well 
document it and close this one as invalid. 
                
> 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

Reply via email to