Mailing-List: contact hbase-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hbase-dev@hadoop.apache.org
Message-ID: <1137581479.1250303174783.JavaMail.jira@brutus>
Date: Fri, 14 Aug 2009 19:26:14 -0700 (PDT)
From: "Vaibhav Puranik (JIRA)" <jira@apache.org>
To: hbase-dev@hadoop.apache.org
Subject: [jira] Commented: (HBASE-1758) Extract interface out of HTable
In-Reply-To: <344961530.1250000415314.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-1758?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12743524#action_12743524 ] 

Vaibhav Puranik commented on HBASE-1758:
----------------------------------------

Great. I will delete the class.

> Extract interface out of HTable
> -------------------------------
>
>                 Key: HBASE-1758
>                 URL: https://issues.apache.org/jira/browse/HBASE-1758
>             Project: Hadoop HBase
>          Issue Type: Improvement
>          Components: client
>            Reporter: Vaibhav Puranik
>             Fix For: 0.21.0
>
>         Attachments: HTableInterface.patch
>
>
> As per discussions in Hackathon, we have extracted interface out of HTable and named it as HTableInterface. This will make unit testing client code easier and simplify client API. 
> It opens other possibilities such as creating a HTable that does not do any RPC calls, MockHTable etc.
> HTablePool still returns HTable instances. But we have added a setter method for HTableInterfaceFactory on it. Thus developers can write their own HTableInterfaceFactory impl to return their own HTableInterface implementation. 
> I have assigned this issue to 0.21 but you may consider it to move it to 0.20 if possible.

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