you should design resilient ETL-processes. Also introduce post-ETL checks. There is no need to test MySQL or HBase. They are already tested. See this: http://www.slideshare.net/wyaddow/data-verification-in-qa-department-final Pretty old, but gives basic ideas. Nothing changed from that time.
2014-08-12 7:55 GMT+04:00 tobe <[email protected]>: > Most of our users migrated their data form MySQL to HBase. Before they > totally trust HBase, they use MySQL and HBase at the same time. Sometimes > the data is inconsistent because they use it incorrectly or maybe there're > bugs of HBase. Anyway, we have to make sure the data from MySQL and HBase > is consistent. > > So how can we do that? Write a simple script or is there any general > method? >
