You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Niels Basjes (JIRA)" <ji...@apache.org> on 2016/08/31 12:53:20 UTC

[jira] [Updated] (HBASE-16536) Make the HBase minicluster easy to use for testing downstream applications.

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

Niels Basjes updated HBASE-16536:
---------------------------------
    Attachment: HBASE-16536-01.patch

This patch move the existing FilterTestingCluster to a more generic location so it is more understandable it can be used for other tests.

In addition the hbase.zookeeper.quorum property properly filled and a  a temporary hbase-site.xml file is generated which is then injected into the classpath.

As a consequence after this has been started any HBase client can simply do HBaseConfiguration.create() and get a config with this testing cluster in it.
So user applications simply need to start this testing cluster by making it the super class of their test class.



> 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
>
>
> 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
(v6.3.4#6332)