When the application creates an entity, it can assign another entity as the
parent of the new entity. Assigning a parent to a new entity puts the new
entity in the same entity group as the parent entity.
I think I need to sign up for app engine and use it to see if I can figure
how the above
So if we wrote all operations for a transaction first to ZooKeeper, we
still need something like a Distributed Transaction Manager to
orchestrate the commit process: Send BatchUpdates to each
RegionServer, ask them to commit, then commit or rollback based on
results from all participating
Clint Morgan wrote:
So if we wrote all operations for a transaction first to ZooKeeper, we
still need something like a Distributed Transaction Manager to
orchestrate the commit process: Send BatchUpdates to each
RegionServer, ask them to commit, then commit or rollback based on
results from all
Clint Morgan wrote:
Responses inline:
2008/5/27 Bryan Duxbury [EMAIL PROTECTED]:
It seems like if you wanted to do some manner of multi-row transactional
put, the only real way to manage it is with deletes. That is, if the first
put succeeds but the second fails, you can invert the first
