[
https://issues.apache.org/jira/browse/HBASE-15321?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16335037#comment-16335037
]
Hudson commented on HBASE-15321:
--------------------------------
FAILURE: Integrated in Jenkins build HBase-Trunk_matrix #4450 (See
[https://builds.apache.org/job/HBase-Trunk_matrix/4450/])
HBASE-15321 - Ability to open a HRegion from hdfs snapshot. (churro: rev
b577fa081430d0d14d86b0aa274abf15243f0f75)
* (add)
hbase-server/src/test/java/org/apache/hadoop/hbase/regionserver/TestHdfsSnapshotHRegion.java
* (edit)
hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/HRegion.java
* (edit)
hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/HRegionFileSystem.java
> Ability to open a HRegion from hdfs snapshot.
> ---------------------------------------------
>
> Key: HBASE-15321
> URL: https://issues.apache.org/jira/browse/HBASE-15321
> Project: HBase
> Issue Type: New Feature
> Affects Versions: 2.0.0, 3.0.0, 1.5.0
> Reporter: churro morales
> Assignee: churro morales
> Priority: Major
> Fix For: 3.0.0, 1.5.0, 2.0.0-beta-2
>
> Attachments: HBASE-15321.patch, HBASE-15321.v01.patch,
> HBASE-15321.v02.patch, HBASE-15321.v1.branch-1.patch
>
>
> Now that hdfs snapshots are here, we started to run our mapreduce jobs over
> hdfs snapshots. The thing is, hdfs snapshots are read-only point-in-time
> copies of the file system. Thus we had to modify the section of code that
> initialized the region internals in HRegion. We have to skip cleanup of
> certain directories if the HRegion is backed by a hdfs snapshot. I have a
> patch for trunk with some basic tests if folks are interested.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)