[
https://issues.apache.org/jira/browse/HBASE-14876?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15281628#comment-15281628
]
Nick Dimiduk commented on HBASE-14876:
--------------------------------------
Perhaps it's helpful: the {{beforeClass}} method of my minicluster tests tends
to look like this:
{noformat}
// HBaseTestingUtility takes care of ZK, HDFS, and HBase
UTIL = HBaseTestingUtility.createLocalHTU();
// disable UI's on test cluster.
UTIL.getConfiguration().setInt("hbase.master.info.port", -1);
UTIL.getConfiguration().setInt("hbase.regionserver.info.port", -1);
UTIL.startMiniCluster();
{noformat}
Minicluster already grabs random ports for RPC, so this last bit allows for
minicluster to launch while a local hbase is concurrently running. Perhaps,
instead, these should be applied by default in {{HBaseTestingUtility}} ?
> Provide maven archetypes
> ------------------------
>
> Key: HBASE-14876
> URL: https://issues.apache.org/jira/browse/HBASE-14876
> Project: HBase
> Issue Type: New Feature
> Components: build, Usability
> Affects Versions: 2.0.0
> Reporter: Nick Dimiduk
> Assignee: Daniel Vimont
> Labels: beginner, maven
> Attachments: HBASE-14876-v2.patch, HBASE-14876.patch,
> archetype_prototype.zip, archetype_prototype02.zip,
> archetype_shaded_prototype01.zip
>
>
> To help onboard new users, we should provide maven archetypes for hbase
> client applications. Off the top of my head, we should have templates for
> - hbase client application with all dependencies
> - hbase client application using client-shaded jar
> - mapreduce application with hbase as input and output (ie, copy table)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
