Yes, although the new Table interface implementation (it really is a HUMBLE but now hidden from you and might change in the future) is using a BufferedMutator internally, it will flush at the end of every operation.
Sent from my iPhone > On 05 Apr 2015, at 11:23, donhoff_h <[email protected]> wrote: > > Hi, Lars > > > Thanks very much for sharing this example. > > > By the way, does that mean the Puts and Deletes I submitted through table.put > and table.delete won't be buffered and will be flushed immediately? > > > > > ------------------ 原始邮件 ------------------ > 发件人: "Lars George";<[email protected]>; > 发送时间: 2015年4月5日(星期天) 下午5:01 > 收件人: "[email protected]"<[email protected]>; > > 主题: Re: HBase1.0 API Problem: setAutoFlush and flushCommits > > > > Hi, > > This has been moved to BufferedMutator. I have an example here: > https://github.com/larsgeorge/hbase-book/blob/master/ch03/src/main/java/client/BufferedMutatorExample.java > > Best, > Lars > >> On Sun, Apr 5, 2015 at 10:49 AM, donhoff_h <[email protected]> wrote: >> >> Hi, experts. >> >> >> I migrated my HBase cluster from version 0.98.10 to version 1.0. I find >> that in HBase1.0 the class "Table" does not contain the API setAutoFlush >> and flushCommits any more. Could anybody tell me where these APIs go? What >> should I do now if I want to make a commitment after some Puts operations? >> >> >> Many Thanks!
