EDIT

I think this is a really good idea. I have been doing some research on this, from the point of of the Data Quality Initiative, but also for the CDM hibernate connection.

It seems that the pushing data from spring-hibernate to elastic search will not be very difficult. In addition to the library you have mentioned, we could also write our own CDM specific Elasticsearch bridge as mentioned here

The above link also mentioned pulling data the other way around, using an Elasticsearch River":http://www.elasticsearch.org/guide/en/elasticsearch/rivers/current/, but there is new project under-development to replace this, called "Gatherer This idea could be useful in certain situations, but probably not for real time editing.

One of the main issues I found with Elasticsearch (related to the CDM) is joins. As mentioned on their page for managing relations the only way to effectively do this is to pre-process the data and store the data as parent-child relationships. This does effect performance and considering the complexity of the CDM, this may not be a good idea for pure CDM entities.

There is already a Elasticsearch Java API for accessing an existing cluster. For the server itself, since Elasticsearch is written in Java and is open source, I'm sure we can find a way to package and launch the Elasticsearch server from within the CDMserver.

From a broader perspective, I think we should separate the so-called 'pure' CDM entities and other DTO objects. We can then index most (if not all) CDM entities in Hibernate Lucene and index all kinds of other objects (only for quick reading) in Elasticsearch. This would be very flexible since we would then do all 'CUD' operations via the CDM and all the 'R' operations via customised DTOs stored in Elasticsearch.

Personally, I am super keen for this idea but it will also be a kind of full-fledged project, so we should discuss this in more detail.