activemq

History

Gary Tully e1389a6acc allow journal write batching, resolve global transaction lock and journal lock, let writes accumulate on the datafileappender rather than at the store, also tie transaction completion and after commit processing together with a callback rather than with a global lock so that concurrent commits can batch their writes - rework of fix for https://issues.apache.org/activemq/browse/AMQ-2594 git-svn-id: https://svn.apache.org/repos/asf/activemq/trunk@947657 13f79535-47bb-0310-9956-ffa450edef68		2010-05-24 14:48:55 +00:00
..
src	allow journal write batching, resolve global transaction lock and journal lock, let writes accumulate on the datafileappender rather than at the store, also tie transaction completion and after commit processing together with a callback rather than with a global lock so that concurrent commits can batch their writes - rework of fix for https://issues.apache.org/activemq/browse/AMQ-2594	2010-05-24 14:48:55 +00:00
README	Moving the kahadb work from the sandbox into trunk now that 5.2 has been released.	2008-11-21 18:19:50 +00:00
pom.xml	AMQ-2602: avoid activemq osgi bundles to import their own packages	2010-02-11 09:57:46 +00:00

README

=======================================================================
 KahaDB : An Embedded Lightweight Non-Relational Database
=======================================================================

Goals:
  * Provide a simple collections based interface for storing persistent
    data.
  * Provide a lower level key value interface for storing data. Secondary
    keys should be supported.
  * Fast recovery

Status:
  * Moved the org.apache.activemq.kaha package into this module
    and renamed it as org.apache.kahadb
  * Moved a refactored version of the low level indexing logic
    used by Apache xindice to the org.apache.kahadb.xindice page.
  
TODO:
  * None of our current index support fast recovery.  They suffer
    from partial page write failures so on a crash, they have
    to be fully rebuilt from the data logs.
  * Indexes should know what the last transaction id that updated
    it, so that missing operations can be replayed. 
  * Investigate implementing data log replication for HA.