hbase-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bryan Duxbury (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HBASE-481) Use smaller dataset in TestTableIndex and TestTableMapReduce
Date Thu, 15 May 2008 21:48:55 GMT

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

Bryan Duxbury commented on HBASE-481:
-------------------------------------

That's a notable improvement. We can live with that for the time being.

To be clear, my previous suggestion was not to use addContent at all. Instead, use the TestRegionRebalancing
approach, and just forge N regions with hardly any rows in them.

> Use smaller dataset in TestTableIndex and TestTableMapReduce
> ------------------------------------------------------------
>
>                 Key: HBASE-481
>                 URL: https://issues.apache.org/jira/browse/HBASE-481
>             Project: Hadoop HBase
>          Issue Type: Sub-task
>            Reporter: Bryan Duxbury
>
> TestTableIndex and TestTableMapReduce rely on MakeMultiRegionTable, which in turn calls
addContent in HBaseTestCase. This method produces 17k rows in the table, and something like
10 regions. That's a lot more than we actually need to prove the functionality of TTI and
TTMR. 
> Can we reduce the number of rows that we use by shortening the run of addContent? Is
there any risk in changing addContent globally to produce less data?

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


Mime
View raw message