You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-dev@hadoop.apache.org by "Jim Kellerman (JIRA)" <ji...@apache.org> on 2008/01/10 02:10:34 UTC
[jira] Updated: (HADOOP-2478) [hbase] restructure how HBase lays
out files in the file system
[ https://issues.apache.org/jira/browse/HADOOP-2478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jim Kellerman updated HADOOP-2478:
----------------------------------
Attachment: patch.txt
Although this won't go in until 0.17, let's get Hudson used to running it. He doesn't like most patches.
> [hbase] restructure how HBase lays out files in the file system
> ---------------------------------------------------------------
>
> Key: HADOOP-2478
> URL: https://issues.apache.org/jira/browse/HADOOP-2478
> Project: Hadoop
> Issue Type: Improvement
> Components: contrib/hbase
> Affects Versions: 0.16.0
> Reporter: Jim Kellerman
> Assignee: Jim Kellerman
> Fix For: 0.16.0
>
> Attachments: patch.txt
>
>
> Currently HBase has a pretty flat directory structure. For example:
> {code}
> /hbase/hregion_70236052/info
> /hbase/hregion_70236052/info/info/4328260619704027575
> /hbase/hregion_70236052/info/mapfiles/4328260619704027575
> /hbase/hregion_70236052/info/mapfiles/4328260619704027575/data
> /hbase/hregion_70236052/info/mapfiles/4328260619704027575/index
> {code}
> All the region directories are under the root directory, and with encoded region names, it is impossible to determine what table a region belongs to. This should be restructured to:
> {code}
> /root-directory/table-name/encoded-region-name/column-family/{info,mapfiles}
> {code}
> It will be necessary to provide a migration script from current trunk to the new structure.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.