jackrabbit-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <wikidi...@apache.org>
Subject [Jackrabbit Wiki] Update of "Transactional model of the Microkernel based Jackrabbit prototype" by MichaelDürig
Date Thu, 24 Nov 2011 11:51:15 GMT
Dear Wiki user,

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

The "Transactional model of the Microkernel based Jackrabbit prototype" page has been changed
by MichaelDürig:
http://wiki.apache.org/jackrabbit/Transactional%20model%20of%20the%20Microkernel%20based%20Jackrabbit%20prototype?action=diff&rev1=3&rev2=4

Comment:
Added section describing commit constraints

                                                    
  To avoid these kind of inconsistencies, the Microkernel needs to impose additional checks
on transactions. A technique which avoids write skew effectively resulting in serializable
histories is described in [2]. 
  
+ Another way to mitigate the problem is to add a constraint checking capability to the Microkernel.
A client would include a specification of its constraint in the commit. The Microkernel would
then determine whether that constraint would still hold after having processed the commit.
If not the commit would simply fail. Note however, that this does not solve the problem for
application constraints encoded in applications on top of the repository. 
+ 
  [1] [[http://http://research.microsoft.com/apps/pubs/default.aspx?id=69541 | A Critique
of ANSI SQL Isolation Levels]]. Hal Berenson, Phil Bernstein, Jim Gray, Jim Melton, Elizabeth
O'Neil, and Patrick O'Neil. June 1995
  
  [2] [[http://dl.acm.org/citation.cfm?id=1376690 | Serializable isolation for snapshot databases]].
Michael J. Cahill, Uwe Röhm, and Alan D. Fekete. 2008.

Mime
View raw message