[
https://issues.apache.org/jira/browse/HBASE-12054?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14146430#comment-14146430
]
Jonathan Hsieh commented on HBASE-12054:
----------------------------------------
great, thanks. +1.
Can you add a release note about which tablenames used to have migration
problems before this fix?
Maybe something like:
Prior to HBase 0.98.7, if you have 0.94 tables named data, archive, corrupt,
lib, WALs, splitWAl, or oldWALs upgrading would fail.
> bad state after NamespaceUpgrade with reserved table names
> ----------------------------------------------------------
>
> Key: HBASE-12054
> URL: https://issues.apache.org/jira/browse/HBASE-12054
> Project: HBase
> Issue Type: Bug
> Affects Versions: 0.96.2, 0.99.0, 0.98.6.1
> Reporter: Matteo Bertozzi
> Assignee: Matteo Bertozzi
> Fix For: 0.98.7, 0.99.1
>
> Attachments: HBASE-12054-0.98.patch, HBASE-12054-branch1.patch,
> HBASE-12054-trunk.patch
>
>
> If 94 has a table called "data" NamespaceUpgrade will fail to bring that
> table up and the generated layout will be dirty with stuff like
> "/hbase/data/.data" and so on.
> (the reserved names that we have no longer apply in 96+ since the data is
> separate from the root dir)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)