testing via htablemock or similar

[du291]

Hello,
what are the options on testing hbase access? I can use scalding's JobTest but that would mock out the whole source. Is there a way to use SpyGlass with some test double for the database, like htablemock? Currently I'm testing against a live hbase, but that's quite non-scalable.

[crajah]

Hi,

SpyGlass doesn't lend itself quite so well to mocked HBase. However, that said, yes, you can use HTableMock to test the implementation. Remember that SpyGlass takes into account region server locality as well as region locality. This has to be mocked I. HTableMock as well to ensure proper functionality in production.

Personally, is create dummy tables in an active HBase system and force splitting to test all functionality.

Cheers,
Chandan

On 2 Jun 2014, at 12:52, du291 notifications@github.com wrote:

Hello,
what are the options on testing hbase? I can use scalding's JobTest but that would mock out the whole source. Is there a way to use SpyGlass with some test double for the database, like htablemock? Currently I'm testing against a live hbase, but that's quite non-scalable.

—
Reply to this email directly or view it on GitHub.

[du291]

Thanks for the response. I'm a little lost with the details though. I guess "force splitting" means to make sure that table has multiple regions? Do you have an example for the HTableMock approach?

[crajah]

Yes. If you use the SPLITS option when creating a table you can be guaranteed to have the splits you created.

create 'tableName', 'cf1', {SPLITS => ['10','20','30','40']}

Cheers,
Chandan

On 2 Jun 2014, at 13:07, du291 notifications@github.com wrote:

Thanks for the response. I'm a little lost with the details though. I guess "force splitting" means to make sure that table has multiple regions? Do you have an example for the HTableMock approach?

—
Reply to this email directly or view it on GitHub.