# Compass migration

**URL:** <https://discuss.elastic.co/t/compass-migration/5058>\
**Category:** Elasticsearch\
**Created:** [August 4, 2011, 11:21pm UTC](https://discuss.elastic.co/t/compass-migration/5058 "2011-08-04T23:21:08Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![Andrew\_Regan](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/andrew_regan/32/3080_2.png) [@Andrew\_Regan](https://discuss.elastic.co/u/Andrew_Regan)\
**Post date:** [August 4, 2011, 11:21pm UTC](https://discuss.elastic.co/t/compass-migration/5058/1 "2011-08-04T23:21:08Z")

</div>

HI all,

I'm still using Compass 2.x (Hibernate GPS integration) but have been keen  
to migrate to Elasticsearch for quite a few months now, so I thought I'd ask  
what the current recommendation is?

1. Wait a bit longer (e.g. months) for a future release of Elasticsearch  
to include Compass-style OSEM, at least something to help migration.
2. Get involved with some of the projects that are covering similar  
ground, e.g. felipera's Play Framework stuff  
([http://geeks.aretotally.in/play-framework-module-elastic-search-distributed-searching-with-json-http-rest-or-java](http://geeks.aretotally.in/play-framework-module-elastic-search-distributed-searching-with-json-http-rest-or-java))
3. Start again from scratch, and manually call Elasticsearch for each  
entity change (not fun!).
4. Stay with Compass - it's fine (I'm not expecting this to be the  
answer).

Any suggestions much appreciated!

---

<div class="post-metadata">

**Author:** ![kimchy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kimchy/32/44952_2.png) [@kimchy](https://discuss.elastic.co/u/kimchy)\
**Post date:** [August 6, 2011, 5:05pm UTC](https://discuss.elastic.co/t/compass-migration/5058/2 "2011-08-06T17:05:57Z")

</div>

Mu suggestion is to get involved with projects that will develop OSEM like  
capabilities and on top of that, Hibernate (or other ORM) integration. My  
hope is that the Java/JVM community will kick in and start developing  
different integrations on top of elasticsearch as has been done in other  
languages.

Note, my plan was to possibly build something similar to OSEM and the ORM  
integration in elasticsearch, but currently, the preference is to focus on  
code elasticsearch features that will benefit a broader set of users, and  
let the community work on addons.

On Fri, Aug 5, 2011 at 2:21 AM, Andrew Regan [aregan@gmail.com](mailto:aregan@gmail.com) wrote:

> HI all,
> 
> I'm still using Compass 2.x (Hibernate GPS integration) but have been keen  
> to migrate to Elasticsearch for quite a few months now, so I thought I'd ask  
> what the current recommendation is?
> 
> 1. Wait a bit longer (e.g. months) for a future release of  
> Elasticsearch to include Compass-style OSEM, at least something to help  
> migration.
> 2. Get involved with some of the projects that are covering similar  
> ground, e.g. felipera's Play Framework stuff (  
> [http://geeks.aretotally.in/play-framework-module-elastic-search-distributed-searching-with-json-http-rest-or-java](http://geeks.aretotally.in/play-framework-module-elastic-search-distributed-searching-with-json-http-rest-or-java)  
> )
> 3. Start again from scratch, and manually call Elasticsearch for each  
> entity change (not fun!).
> 4. Stay with Compass - it's fine (I'm not expecting this to be the  
> answer).
> 
> Any suggestions much appreciated!

---

<div class="post-metadata">

**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\
**Post date:** [August 8, 2011, 7:28pm UTC](https://discuss.elastic.co/t/compass-migration/5058/3 "2011-08-08T19:28:05Z")

</div>

Alois starts a really good job about OSEM / ES :  
[https://github.com/aloiscochard/elasticsearch-osem](https://github.com/aloiscochard/elasticsearch-osem)

> **[aloiscochard/elasticsearch-osem](https://github.com/aloiscochard/elasticsearch-osem)**
>
> elasticsearch-osem - ElasticSearch OSEM

You can have a look at this and see if you can use it. There are some tests  
cases that really help to understand how it works.

Hope this helps,

David.

De : [elasticsearch@googlegroups.com](mailto:elasticsearch@googlegroups.com) [[mailto:elasticsearch@googlegroups.com](mailto:elasticsearch@googlegroups.com)]  
De la part de Shay Banon  
Envoyé : samedi 6 août 2011 19:06  
À : [elasticsearch@googlegroups.com](mailto:elasticsearch@googlegroups.com)  
Objet : Re: Compass migration...

Mu suggestion is to get involved with projects that will develop OSEM like  
capabilities and on top of that, Hibernate (or other ORM) integration. My  
hope is that the Java/JVM community will kick in and start developing  
different integrations on top of elasticsearch as has been done in other  
languages.

Note, my plan was to possibly build something similar to OSEM and the ORM  
integration in elasticsearch, but currently, the preference is to focus on  
code elasticsearch features that will benefit a broader set of users, and  
let the community work on addons.

On Fri, Aug 5, 2011 at 2:21 AM, Andrew Regan [aregan@gmail.com](mailto:aregan@gmail.com) wrote:

HI all,

I'm still using Compass 2.x (Hibernate GPS integration) but have been keen  
to migrate to Elasticsearch for quite a few months now, so I thought I'd ask  
what the current recommendation is?

1. Wait a bit longer (e.g. months) for a future release of  
Elasticsearch to include Compass-style OSEM, at least something to help  
migration.
2. Get involved with some of the projects that are covering similar  
ground, e.g. felipera's Play Framework stuff  
([http://geeks.aretotally.in/play-framework-module-elastic-search-distributed](http://geeks.aretotally.in/play-framework-module-elastic-search-distributed)  
-searching-with-json-http-rest-or-java)
3. Start again from scratch, and manually call Elasticsearch for each  
entity change (not fun!).
4. Stay with Compass - it's fine (I'm not expecting this to be the  
answer).

Any suggestions much appreciated!

---

<div class="post-metadata">

**Author:** ![Andrew\_Regan](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/andrew_regan/32/3080_2.png) [@Andrew\_Regan](https://discuss.elastic.co/u/Andrew_Regan)\
**Post date:** [August 9, 2011, 10:57am UTC](https://discuss.elastic.co/t/compass-migration/5058/4 "2011-08-09T10:57:11Z")

</div>

Thanks, Shay and David, I'll have a look at Alois's project and try to get  
something up and running. If I get the Hibernate integration layer working  
I'll contribute it to the community.

Andrew

---

<div class="post-metadata">

**Author:** ![Andrew\_Regan](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/andrew_regan/32/3080_2.png) [@Andrew\_Regan](https://discuss.elastic.co/u/Andrew_Regan)\
**Post date:** [August 15, 2011, 11:51am UTC](https://discuss.elastic.co/t/compass-migration/5058/5 "2011-08-15T11:51:21Z")

</div>

Just a quick update to mention my new OSEM/Hibernate integration project:

> **[poblish/elasticsearch-osem](https://github.com/poblish/elasticsearch-osem)**
>
> elasticsearch-osem - ElasticSearch OSEM with Hibernate-ORM integration

Essentially what I've done is extract the gps/device/Hibernate code from the  
final version of Compass, breaking the dependencies on the high-level  
Compass interfaces, and commenting-out the mapping, resource, and  
transaction calls until I had something that would build standalone (well,  
build against Hibernate 3.6 and Lucene 3.3). A bit of a hack, perhaps, but I  
figured that the Compass Hib code is tried and tested, and worth saving  
where possible.

I merged the results into my fork of Alois's elasticsearch-osem project,  
leaving me the challenge of replacing the commented-out mapping, resource,  
transaction, etc. stuff with the ElasticSearch/OSEM replacements. While I'm  
doing this I'll also be refactoring to remove stuff that's obsolete, and  
trying to ensure that the Hibernate and GPS code fits in properly with the  
ES model.

Very early days, so help and advice (and integration tests) much  
appreciated!

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [July 6, 2017, 3:56am UTC](https://discuss.elastic.co/t/compass-migration/5058/6 "2017-07-06T03:56:57Z")

</div>


