So you are using explicit time stamps for the put calls? Is this related to
https://issues.apache.org/jira/browse/HBASE-3300 by any chance? You have to be extra careful with explicit timestamps as newer deletes can mask readding puts that have an older timestamp. Try this: 1. Do the MR job 2. Do the delete from the shell 3. Check that it was deleted from the shell 4. Run a major compaction of the table on the shell (e.g. "major_compact <tablename>") 5. Re-run the MR job 6. Check if the value is there again. And finally let us know here :) Lars On Thu, Dec 2, 2010 at 2:48 AM, 梁景明 <[email protected]> wrote: > 0.20.6 > > 2010/12/2 Lars George <[email protected]> > >> What version of HBase are you using? >> >> On Dec 1, 2010, at 9:24, 梁景明 <[email protected]> wrote: >> >> > i found that if i didnt control timestamp of the put >> > mapreduce can run, otherwise just one time mapreduce. >> > the question is i scan by timestamp to get my data >> > so to put timestamp is my scan thing. >> > >> > any ideas ? thanks. >> > >> > 2010/12/1 梁景明 <[email protected]> >> > >> >> Hi,i found a problem in my hbase mapreduce case. >> >> >> >> when first running mapreduce TableMapReduceUtil runs ok. >> >> >> >> and i use hbase shell to delete some data from the table that mapreduce >> one >> >> . >> >> >> >> then ran mapreduce to insert some new data. >> >> >> >> no thing data changed, mapreduce didnt work. >> >> >> >> after that i drop the table and recreate it >> >> >> >> run mapreduce again ,data inserted successful. >> >> >> >> what happen to mapreduce . >> >> >> >> Is it only can insert table just one time? >> >> >> >
