-
Notifications
You must be signed in to change notification settings - Fork 31
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
testing via htablemock or similar #13
Comments
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,
|
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? |
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,
|
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.
The text was updated successfully, but these errors were encountered: