Mailing-List: contact hbase-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hbase-dev@hadoop.apache.org
Message-ID: <1312472994.1206386004423.JavaMail.jira@brutus>
Date: Mon, 24 Mar 2008 12:13:24 -0700 (PDT)
From: "Bryan Duxbury (JIRA)" <jira@apache.org>
To: hbase-dev@hadoop.apache.org
Subject: [jira] Updated: (HBASE-536) Remove MiniDFS startup from
 MiniHBaseCluster
In-Reply-To: <1232147798.1206058284624.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/HBASE-536?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Bryan Duxbury updated HBASE-536:
--------------------------------

    Resolution: Fixed
        Status: Resolved  (was: Patch Available)

I just committed a version of this patch that incorporated stack's suggestions and hadoop-first patch.

> Remove MiniDFS startup from MiniHBaseCluster
> --------------------------------------------
>
>                 Key: HBASE-536
>                 URL: https://issues.apache.org/jira/browse/HBASE-536
>             Project: Hadoop HBase
>          Issue Type: New Feature
>          Components: test
>            Reporter: Bryan Duxbury
>            Assignee: Bryan Duxbury
>            Priority: Minor
>             Fix For: 0.2.0
>
>         Attachments: 536.patch, hadoop_first.patch
>
>
> Change MiniHBaseCluster to always require a MiniDfs started elsewhere. It will decide where to read and write based on the config passed in to its constructor. 
> HBaseClusterTestCase will be updated to do the MiniDFS spinup and shutdown as part of its normal process.
> Completing this issue will prime us for solving the truly external DFS issue for making the test suite faster. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.