Lets ask a better question… why?

Are you trying to clean your data? In which case, by removing the row of ‘bad’ data, you lose your auditing. (But that will depend on if you need to audit your data, and how you’re auditing it…)

Is the timestamp important? If so, why not capture it as an attribute of your data.
This way you have the timestamp of the row, (hbase) and then the column.

If you do this, you can capture both the timestamp associated with the data, and then the time it was entered in to your system.

Does that make sense?

-Mike
The opinions expressed here are mine, while they may reflect a cognitive thought, that is purely accidental.
Use at your own risk.
Michael Segel
michael_segel (AT) hotmail.com
NEW: Monitor These Apps!
elasticsearch, apache solr, apache hbase, hadoop, redis, casssandra, amazon cloudwatch, mysql, memcached, apache kafka, apache zookeeper, apache storm, ubuntu, centOS, red hat, debian, puppet labs, java, senseiDB