Mailing-List: contact core-commits-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: core-dev@hadoop.apache.org
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: Apache Wiki <wikidiffs@apache.org>
To: core-commits@hadoop.apache.org
Date: Fri, 18 Jul 2008 22:02:03 -0000
Message-ID: <20080718220203.24339.52142@eos.apache.org>
Subject: [Hadoop Wiki] Update of "Hbase/Plan-0.2/APIChanges" by izaakrubin

Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Hadoop Wiki" for change notification.

The following page has been changed by izaakrubin:
http://wiki.apache.org/hadoop/Hbase/Plan-0%2e2/APIChanges

------------------------------------------------------------------------------
  
  `startUpdate(Text)` was used to start an atomic row update on the passed row name, and a "lock id" (`long`) was returned to identify the update.  `put(...)` and `delete(...)` could be called using the lock id, and any changes made with that lock id could be aborted or committed.
  
- HBase 0.2 has completely changed the way in which atomic row updates take place.  To update a row, the user first creates a `BatchUpdate` object (new to 0.2, package `org.apache.hadoop.hbase.io`).  `put(...)` and `delete(...)` operations are applied to the `BatchUpdate`, not the `HTable`.  Once finished, the user commits the `BatchUpdate` with one of the following new `HTable` methods:
+ HBase 0.2 has completely changed the way in which atomic row updates take place.  To update a row, the user first creates a `BatchUpdate` object.  `put(...)` and `delete(...)` operations are applied to the `BatchUpdate`, not the `HTable`.  Once finished, the user commits the `BatchUpdate` with one of the following new `HTable` methods:
  
  ''0.2:''
  [[BR]] {{{public synchronized void commit(BatchUpdate);}}}