Not sure if you already know this, but at the core of Hippo repository
is the JackRabbit repository, which in turn has various
implementations  of storage for content (nodes and properties).
The question you ask was asked on the jackrabbit mailinglist a while
ago  for couchdb and mongodb. According to the answer, the
implementation shouldn't be that hard, but nobody saw a reason to do
On Thu, Jun 2, 2011 at 5:14 PM, M Nair <[hidden email]> wrote:
> I know Hippo supports SQL databases and the in-build Derby follows SQL
> standards,, I am wondering if Hippo supports non SQL databases like NoSQL etc..
> Just wanted to verify as this question came up..
> Hippo-cms7-user mailing list and forums
> http://www.onehippo.org/cms7/support/forums.html >
Hippo-cms7-user mailing list and forums
there has been work on running Hippo on an in memory data grid; I've
witnessed this presentation:
http://vimeo.com/channels/hippogettogether#15119704 Not quite what you're looking for, I realize, but they seem to have
implemented this without too much trouble.
There were some problems distributing the index, IIRC, but I'm not
sure that's the right approach anyway. Probably better to leave that
to a distributed search engine anyway. (e.g. solr or elastic search)