What about just storing some metadata in a special table?
Then on you second job startup you can read that meta data and set your scan
/input splits appropriately?
Dave
-Original Message-
From: Vishal Kapoor [mailto:vishal.kapoor...@gmail.com]
Sent: Friday, March 25, 2011 11:21 AM
To:
...@gmail.com]
Sent: Friday, March 25, 2011 3:00 PM
To: user@hbase.apache.org
Cc: Buttler, David
Subject: Re: Observer/Observable MapReduce
David,
how about waking up my second map reduce job as soon as I see some rows updated
in that table.
any thoughts on observing a column update?
thanks
Instead of using a table, how about using the available ZooKeeper
service itself? They can hold small bits of information pretty well
themselves.
On Sat, Mar 26, 2011 at 12:29 AM, Vishal Kapoor
vishal.kapoor...@gmail.com wrote:
David,
how about waking up my second map reduce job as soon as I
