scan can early exit for incrementColumnValue()
Review Request #1053 - Created Oct. 20, 2010 and updated
Ensure that during incrementColumnValue() the scan triggered by the get() does an early exit if it finds the KV in the memstore.
I have been testing it on my cluster. No unit testing yet.
Posted (Oct. 20, 2010, 5 a.m.)
Need to add apache licenses
Maybe a little more description here. Like, why do we need this. Also, is ControlledScan the best name for this class? Not clear to me that this is "controlled" and thus the other scans are "uncontrolled"? If this was to be used for more later and even for this use, it's really additional configuration/options for Scans. So is an InternalScan or ModifiedScan?
Rather than these two public booleans, we should have getters/setters. And even rather than just straight set/get on each boolean, these two booleans are usually one or the other, right? So I think it would be better to hide implementation detail and instead expose methods like setMemStoreOnly() and setFilesOnly() which would deal with the two booleans appropriately. Then you'd have get methods like checkMemStore() and checkFiles() or something like that.
Need to cleanup whitespace here. Maybe a little bit of javadoc for get\_last\_increment which describes what this does (and why it's still "correct" for increments)
Posted (Oct. 20, 2010, 5:52 a.m.)
Just some minor comments.
Review request changed
Updated (Oct. 20, 2010, 2:31 p.m.)
I think I have taken care of all the review feedback
Revision 2 (+130 -11)
Posted (Oct. 20, 2010, 2:41 p.m.)