Hi,
I am building a web service that looks up data
from several HBase tables and returns a result. There will be an hourly
batch process that generates new versions of the tables, and, when
they’re available, the web service should switch over to using them. The
switchover cannot introduce any interruption or latency into the web
service.
I have considered that if the new version of a
table has the exact same column families as the old table, the batch
process could simply update the old table while it is still in use by the
service, and then do a delete scan (to delete rows
that are in the old version of the table but not in the new version). But I
believe I have a case
where column families could be added or deleted in the new table
version, which is why I’m looking at creating a new table and switching
over to it.
What’s the preferred strategy for implementing
this type of table switching? Is a non-blocking table rename possible?
If not, what’s better?
Thanks much.
_________________________________________________________________
Your E-mail and More On-the-Go. Get Windows Live Hotmail Free.
http://clk.atdmt.com/GBL/go/201469229/direct/01/
