hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Niels Basjes (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-16536) Make the HBase minicluster easy to use for testing downstream applications.
Date Fri, 02 Sep 2016 08:36:20 GMT

    [ https://issues.apache.org/jira/browse/HBASE-16536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15457942#comment-15457942

Niels Basjes commented on HBASE-16536:

In the original location it was put there to 'only' support testing Filters. 

With the new name and new location I attempted to indicate that this class will automatically
start a 'generic' HBase cluster for testing in general.

The idea is that an application that uses HBase and needs to test against it can simply add
the hbase-server 'tests' jars as test dependency and simply use it in their unit tests.

What name and package would you suggest?

> Make the HBase minicluster easy to use for testing downstream applications.
> ---------------------------------------------------------------------------
>                 Key: HBASE-16536
>                 URL: https://issues.apache.org/jira/browse/HBASE-16536
>             Project: HBase
>          Issue Type: Improvement
>            Reporter: Niels Basjes
>            Assignee: Niels Basjes
>         Attachments: HBASE-16536-01.patch, HBASE-16536-02.patch
> In many applications I write I use HBase to store information.
> A big problem is testing these applications.
> I have seen several situations where people have written tests that create tables in
the development cluster and due to firewalls and such couldn't run those tests from Jenkins.
> A while ago I wrote the FilterTestingCluster class that makes unit testing the client
side filters a lot easier. With this ticket I propose to make this more generic and make it
so that user applications can easily incorporate it into their own unit tests without any
major modifications to their application.

This message was sent by Atlassian JIRA

View raw message