I have a follow up question here: A column family can be defined to have a maximum number of versions per column qualifier value. Is this enforced only by the client side code (HTable) or also by the InternalScanner implementations?
On Monday, January 14, 2013, S Ahmed wrote: > Thanks Lars! > > Sort of a side question after following your proposed patch: > https://issues.apache.org/jira/secure/attachment/12511771/5268-v5.txt > > Locally on your computer (laptop?), can those tests run in isolation or you > need a fairly complicated setup to run them? (all the various hbase > dependancies like zookeeper etc). > > > On Sun, Jan 13, 2013 at 9:33 PM, lars hofhansl > <[email protected]<javascript:;>> > wrote: > > > Does this help: > > http://hadoop-hbase.blogspot.com/2012/01/scanning-in-hbase.html ? > > > > > > > > > > ________________________________ > > From: S Ahmed <[email protected] <javascript:;>> > > To: [email protected] <javascript:;> > > Sent: Sunday, January 13, 2013 7:24 AM > > Subject: best read path explanation > > > > What is the best hbase read path explanation? > > > > I understand that hbase stores data and doesn't allow for mutations, so > I'm > > confused as to how a read can get the latest data? > > > > I'm guessing there are merges done between the immutable file stores, and > > in-memory stores? > > >
