jackrabbit-oak-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Tyson Norris <tnor...@adobe.com>
Subject oak's consistency tuning options
Date Fri, 31 Aug 2012 23:08:48 GMT
Hi  -
I was wondering if there are plans to surface consistency options in oak such that certain
save() operations can be guaranteed to be replicated?

For example, in mongo getLastError() [0] can be executed with parameters to indicate that
the call will block until a certain level of consistency is achieved (write has reached the
server, write has been replicated to n nodes, write has been written to journal, etc)

Are there any examples of how oak might provide this type of function, so that applications
could implement features where certain write operations block until consistency is achieved,
and other write operations never block?



  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message