[jira] [Commented] (HBASE-8816) Add support of loading multiple tables into LoadTestTool

["Hadoop QA (JIRA)" <ji...@apache.org>]

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

Hadoop QA commented on HBASE-8816:
----------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12589996/hbase-8816.patch
  against trunk revision .

    {color:green}+1 @author{color}.  The patch does not contain any @author tags.

    {color:green}+1 tests included{color}.  The patch appears to include 3 new or modified tests.

    {color:red}-1 patch{color}.  The patch command could not apply the patch.

Console output: https://builds.apache.org/job/PreCommit-HBASE-Build/6160//console

This message is automatically generated.
                
> Add support of loading multiple tables into LoadTestTool
> --------------------------------------------------------
>
>                 Key: HBASE-8816
>                 URL: https://issues.apache.org/jira/browse/HBASE-8816
>             Project: HBase
>          Issue Type: Test
>          Components: test
>    Affects Versions: 0.94.9
>            Reporter: Jeffrey Zhong
>            Assignee: Jeffrey Zhong
>            Priority: Minor
>         Attachments: hbase-8816.patch
>
>
> Introducing an optional parameter 'concurrent_factor' into LoadTestTool. When it's specified with positive integer n, LoadTestTool will load n tables parallely. -tn parameter value becomes table name prefix. Tables are created with name in format <tn>_1...<tn>_n. A sample command line "-tn test -concurrent_factor 2" will create & load tables:"test_1" and "test_2"
> The motivation is to add a handy way to load multiple tables concurrently. In addition, we could use this option to test resource leakage of long running clients.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira