[ 
https://issues.apache.org/jira/browse/CAMEL-12628?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Claus Ibsen resolved CAMEL-12628.
---------------------------------
       Resolution: Fixed
         Assignee: Claus Ibsen
    Fix Version/s: 2.23.0

The up-to-date doc is at

[https://github.com/apache/camel/blob/master/components/camel-hawtdb/src/main/docs/hawtdb.adoc]

I have updated it and marked it more as deprecated and also removed that part 
about AMQ

> [doc] camel-hawtdb documentation should be updated
> --------------------------------------------------
>
>                 Key: CAMEL-12628
>                 URL: https://issues.apache.org/jira/browse/CAMEL-12628
>             Project: Camel
>          Issue Type: Improvement
>          Components: camel-hawtdb, documentation
>    Affects Versions: 2.22.0
>            Reporter: Torsten Mielke
>            Assignee: Claus Ibsen
>            Priority: Major
>              Labels: camel-hawtdb, documentation
>             Fix For: 2.23.0
>
>
> The documentation for [camel-hawtdb |http://camel.apache.org/hawtdb.html]says:
> {quote}
> The [HawtDB|http://hawtdb.fusesource.org/] project is being deprecated and 
> replaced by [leveldb|https://code.google.com/p/leveldb/] as the lightweight 
> and embedable key value database. To make using leveldb easy there is a 
> [leveldbjni|https://github.com/fusesource/leveldbjni] project for that. The 
> Apache ActiveMQ project is planning on using leveldb as their primary file 
> based message store in the future, to replace kahadb.
> {quote}
> The last part about ActiveMQ replacing KahaDB with LevelDB is out of date. 
> LevelDB has been deprecated on ActiveMQ and KahaDB remains the standard 
> persistence adapter. The top level warning on 
> http://activemq.apache.org/leveldb-store.html. 
> So I suggest to remove that sentence at minimum.
> Also, I am not sure do we still recommend LevelDB as an alternative to hawtdb 
> or would there be even better options these days? 
>  
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to