Compass migration


(Andrew Regan) #1

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)
  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!


(Shay Banon) #2

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 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
    )
  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!


(David Pilato) #3

Alois starts a really good job about OSEM / ES :
https://github.com/aloiscochard/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]
De la part de Shay Banon
Envoyé : samedi 6 août 2011 19:06
À : 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 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)
  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!


(Andrew Regan) #4

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


(Andrew Regan) #5

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

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!


(system) #6