If you just need a sample of rows from tables, use the client API (e.g., HTable) and scan off a few hundred rows or whatever you need. The harder part of local unit testing is getting a coherent set of rows that makes sense between all the tables - but that's something that every developer has to figure out for themselves and their application.
On 8/21/11 8:17 AM, "[email protected]" <[email protected]> wrote: >Hi, > >We have an HBase cluster containing TBs of data. As a front-end >developer, I >need a snippet of some tables to run tests on local. I would like to >build a >script that would export a given number of rows for a given list of >tables. >I had a look at the export / import table but it export the whole table. >Could you suggest me any tool / options that might help me doing this? > >Thanks a lot! >Vincent
