[
https://issues.apache.org/jira/browse/HBASE-11064?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Enis Soztutar updated HBASE-11064:
----------------------------------
Resolution: Fixed
Fix Version/s: (was: 0.98.5)
(was: 1.0.0)
2.0.0
Hadoop Flags: Reviewed
Status: Resolved (was: Patch Available)
I've run the tests manually, and committed this to master and 0.99.
[[email protected]] do you want this in 0.98?
Thanks Rekha for the patch.
> Odd behaviors of TableName for empty namespace
> ----------------------------------------------
>
> Key: HBASE-11064
> URL: https://issues.apache.org/jira/browse/HBASE-11064
> Project: HBase
> Issue Type: Bug
> Affects Versions: 0.98.3
> Reporter: Hiroshi Ikeda
> Assignee: Rekha Joshi
> Priority: Trivial
> Fix For: 0.99.0, 2.0.0
>
> Attachments: HBASE-11064.1.patch, HBASE-11064.2.patch,
> HBASE-11064.2.patch, HBASE-11064.3.patch
>
>
> In the class TableName,
> {code}
> public static byte [] isLegalFullyQualifiedTableName(final byte[] tableName) {
> ...
> int namespaceDelimIndex = ...
> if (namespaceDelimIndex == 0 || namespaceDelimIndex == -1){
> isLegalTableQualifierName(tableName);
> } else {
> ...
> {code}
> That means, for example, giving ":a" as the argument throws an exception
> which says invalid qualifier, instead of invalid namespace.
> Also, TableName.valueOf(String) and valueOf(byte[]) can create an instance
> with empty namespace, which is inconsistent.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
