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

Francis Liu commented on HBASE-8015:
------------------------------------

[~saint....@gmail.com] I've pushed changes into github, the changes mainly 
addresses one thing: make namespace as first class. I've replaced internal apis 
which took "byte[] tableName" as a constant to use FullyQualifiedTableName 
instead. For HTable and HBaseAdmin, I've overloaded such functions instead to 
keep backward compatibility. Also created a new branch in the repo which is a 
rebase off trunk yesterday. I'll address your RB comments today.

Some issues:
- The external interfaces: cli, thrift, rest and MR don't have the namespace as 
first class treatment yet
- I initially went by the InterfaceAudience annotations but after talking to 
you guys it seems this is needs some updating as HConnection and 
HConnectionManager are both marked public tho they shouldn't be?
- There are some apis (ie compact()) which have an overloaded parameter ie 
"byte[] tableOrRegionName" should we be splitting this into two apis and 
deprecate the old one?
- Need to create a FullyQualifiedTableName PB equivalent and update PB rpc and 
messages as needed
- I always needed to add commons-io as a maven dependency else things won't 
compile and these aren't related to my changes
- Ran small,med,large tests and have these failures which aren't related to the 
patch: TestHCM.testClusterStatus, 
TestLogRolling.testCompactionRecordDoesntBlockRolling, TestShell










                
> Support for Namespaces
> ----------------------
>
>                 Key: HBASE-8015
>                 URL: https://issues.apache.org/jira/browse/HBASE-8015
>             Project: HBase
>          Issue Type: New Feature
>            Reporter: Francis Liu
>            Assignee: Francis Liu
>         Attachments: HBASE-8015_draft_94.patch, Namespace Design.pdf
>
>


--
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