I've been giving it a spin during the past couple days and so far
it's been running smooth, I'm using the binaries from your maven repo.
This is a great advance on this direction. (I haven't been able to
compile via maven for some odd reason, I think it's related to the
testng.. I'll check on that later and give you feedback)
Here are my two cents, some of them might be out of the scope now, but
I'll mention them just for the record.
- I think, it'll be nice to have a way to scan entities for
"@Searchable" ala old Compass way :), although this was part of
CompassGPS (I think...)
- re:"@Indexable": Compass used to have 3 different ones (correct me
if I'm wrong):
Just for the sake of compatibility and easiness to migrate from
Compass, it would be nice to have them here as well
I've got a question about _id and its relation with entities:
- Being that my entity has an "id" I'd really like to use that in ES w/
out giving it explicitly, isn't that a desirable behavior while
dealing with entities?
I tried the following, but run into an exception. I assigned
"@Indexable(indexName="_id")" to the setter of my entity id then, I
tried to index it with a simple "client.prepareIndex(INDEX, DOC_TYPE)"
and ES barked at me with
"Caused by: org.elasticsearch.index.mapper.MapperParsingException:
Failed to parse [_id]"
am I having some wrong understanding here?
On May 17, 9:14 am, Alois Cochard alois.coch...@gmail.com wrote:
Just to let you know that I've splitted the OSEM part from my fork
until it get perhaps integreted in ES.
Since I didn't changed anything in ES to implement OSEM, you can use
it as in independent module (and anyone who want to reuse annotations
can do so).
More informations here (only snapshots release for the moment):https://github.com/aloiscochard/elasticsearch-osem
Would be happy to get some feedback if anyone try it.
PS: will blog about it in few days, with a full usage sample