What do you mean "after it ends"? If you call HTable.close(), that then calls flushCommits().
Currently Delete operations are not buffered on the client side, only Puts are. > -----Original Message----- > From: Vidhyashankar Venkataraman [mailto:vidhy...@yahoo-inc.com] > Sent: Tuesday, June 08, 2010 2:24 PM > To: user@hbase.apache.org > Subject: Re: Reads of a recently written/modified value > > Misunderstood about the flush option then.. Thanks for clarifying: > > So, why doesn't the flush option include Delete operations? Why only > Put operations? > And shouldn't the client flush after it ends? > > Vidhya > > On 6/8/10 2:03 PM, "Ryan Rawson" <ryano...@gmail.com> wrote: > > Turning auto flush off will cause the client to accumulate puts without > sending them to the server. Gets and scans only talk to the server and > thus > ignore the client write cache. > > On Jun 8, 2010 1:55 PM, "Vidhyashankar Venkataraman" <vidhy...@yahoo- > inc.com> > wrote: > I was trying to execute some operations on a Hbase instance. After > performing a dozen write operations (with auto flush not set), Hbase > could > not read the inserted/modified records successfully (using the Get > operations). > But with auto flush set and after writing the records, I could read > the > records. > > However, in either case, I could get delete operations successfully > done. > > Is it because the read operations arent reading from the memory? Can > you > guys let me know if I am missing something? > > > Vidhya
