On Thu, Oct 13, 2011 at 1:47 PM, Norbert Burger <[email protected]>wrote:
> > > BTW, can your app support the semantics of having auto flush off? What's > > your use case like? > > > > By semantics, do you mean the possibility that unflushed data might be lost > if the client goes away? Yep, or if the Thrift server dies with unflushed data. > Our app pulls from a queue that supports > acknowledgement, so that side is ok. But as you may be pointing out, we > can > only fire receipt acknowledgement on explicit buffer flushes (eg., > flushCommit()) , so we'd have to somehow disable implicit flushing (because > the write buffer filled up). Thanks for the heads-up. Yeah, you might instead want to just push big batches of data through the equivalent of a batch Put that HTable offers... but that is also missing from the Thrift API. J-D >
