[HBASE-339] [hbase] restructure how HBase lays out files in the file system

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Assignee: Unassigned
• Reporter: Jim Kellerman
• Created: 20/Dec/07 22:07
• Updated: 22/Aug/08 21:35
• Resolved: 13/Jan/08 01:53

Description

Currently HBase has a pretty flat directory structure. For example:

 /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

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:

/root-directory/table-name/encoded-region-name/column-family/{info,mapfiles}

It will be necessary to provide a migration script from current trunk to the new structure.

Issue Links

• blocks: HBASE-395 [hbase] Refactor HStore and internal (and related) classes into hbase.store subpackage
• incorporates: HBASE-66 Add support for migrating between hbase versions
• is part of: HBASE-7 [hbase] Provide a HBase checker and repair tool similar to fsck