That's right. If you ever see more versions than the family setting of maxVersions, something is broken in the read path and we should fix it.
> -----Original Message----- > From: Lars George [mailto:lars.geo...@gmail.com] > Sent: Friday, April 09, 2010 12:58 AM > To: hbase-dev@hadoop.apache.org > Subject: Re: About Hbase > > Oh, discussing this here it seems I was to fast to answer. The Scan > object will set Store.versionsToReturn() to the set max versions. So > have also no idea what the issue is :) > > Please rephrase. > > Lars > > On Fri, Apr 9, 2010 at 9:27 AM, Lars George <lars.geo...@gmail.com> > wrote: > > Hi, > > > >>> The third is about the hbase shell, which implements an alter > command, > >>> that can change or add or delete a column family,but i remember the > column > >>> family cannot be changed after the table is created. I also want > to know > >>> default max VERSIONs, when i create a table i give the VERSION > 2,later i put > >>> three values for the same row+column and different timestamp, but i > can get > >>> values rather than only two. > >> > >> The column family can be changed, not sure what you are referring > to. > >> > >> Default max versions is 3, the rest of the question is > unintelligible. > > > > I think he means he has set Versions to 2 but sees more than those 2. > > That is because the table has not yet been compacted. Run a major > > compaction from the shell on that table and it will reduce the > > versions to the enforced 2. Bottomline is, for a short period of time > > (but can be hours, the default is < 24hrs), you may see more than the > > set number of Versions. Think of it in terms of "Max. number of > > versions to keep". > > > > HTH, > > Lars > >
