Re: thirft mutateRows transaction

2010-12-12 Thread Chris Tarnas
Thanks for the explanation Ryan. -chris On Dec 12, 2010, at 3:16 PM, Ryan Rawson wrote: > Ok javadoc cruft ahoy. > > So back to the core issue about persistence, we promise that if we ack > that your data won't be lost (IF you are running under an > HDFS-200/append qualified hdfs, cdh3b2+ is on

Re: thirft mutateRows transaction

2010-12-12 Thread Ryan Rawson
Ok javadoc cruft ahoy. So back to the core issue about persistence, we promise that if we ack that your data won't be lost (IF you are running under an HDFS-200/append qualified hdfs, cdh3b2+ is one such, building from the append-20-branch in ASF is another). But what happens if the regionserver

Re: thirft mutateRows transaction

2010-12-11 Thread Chris Tarnas
It surprised me when I read it and wondered if something special was going on for the Thrift API. I saw the comment in the Hbase.thrift API file here: http://svn.apache.org/viewvc/hbase/trunk/src/main/resources/org/apache/hadoop/hbase/thrift/Hbase.thrift?view=markup Look at the comment for the m

Re: thirft mutateRows transaction

2010-12-11 Thread Stack
Where do you see that? HBase is not transactional. Thanks Chris, St.Ack On Fri, Dec 10, 2010 at 2:57 PM, Chris Tarnas wrote: > I was looking through the thirft API again and noticed that it said if a > transaction - comprised of updates to one or more rows - throws an exception > then the whol

thirft mutateRows transaction

2010-12-10 Thread Chris Tarnas
I was looking through the thirft API again and noticed that it said if a transaction - comprised of updates to one or more rows - throws an exception then the whole transaction is aborted. Does this mean that it is atomic and none of the updates will be executed or could some subset of them be e