[
https://issues.apache.org/jira/browse/HBASE-1195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12701877#action_12701877
]
Evgeny Ryabitskiy edited comment on HBASE-1195 at 4/23/09 3:11 AM:
-------------------------------------------------------------------
Fixed FSUtils.checkVersion(fs, rootdir, true);
Changes:
* If root dir empty (no version file and no ROOT Region dir), just create new
version file
* But if there exists ROOT Region dir and no Version file, should be required
migration.
Not changed:
* if version not matched ask for migration
was (Author: apparition):
Fixed FSUtils.checkVersion(fs, rootdir, true);
Changes:
* If root dir empty (no version file and no ROOT Region dir), just create new
version file
* But if there exists ROOT Region dir and no Version file, should be required
migration.
Not changed:
* if version not matched ask for
> If HBase directory exists but version file is inexistent, still proceed with
> bootstrapping
> ------------------------------------------------------------------------------------------
>
> Key: HBASE-1195
> URL: https://issues.apache.org/jira/browse/HBASE-1195
> Project: Hadoop HBase
> Issue Type: Improvement
> Components: master
> Reporter: Jean-Daniel Cryans
> Assignee: Evgeny Ryabitskiy
> Priority: Minor
> Fix For: 0.20.0
>
> Attachments: HBASE-1195.patch
>
>
> On the dev list I suggested we change the way we manage the empty HBase
> directory case. Stack answered:
> {quote}
> Yes. In fact, its probably safe-to-do now we've left far behind the
> pre-history versions of hbase where there was no hbase.version file in the
> hbase.rootdir. If absent, lets proceed and just write it rather than treat
> it as a non-migrated instance
> {quote}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
