Good idea.
On Tue 2016-03-15 17:21, Davide D'Alto wrote:
> At the moment the elasticsearch integration artifactid is:
>
> hibernate-search-backend-elasticsearch
>
> Elasticsearch is actually more than just a backend (we use this term for
> the jGroups and JMS integration). I think we should rena
Works for me.
When declaring the original artifact id, I considered the actual
indexing service (Lucene, Elasticsearch, Solr) as the "backend", but I
see how that term already is used for different "worker strategies"
(Local/In-VM, JMS, JGroups).
2016-03-15 19:17 GMT+01:00 Sanne Grinovero :
> On
On 15 March 2016 at 17:21, Davide D'Alto wrote:
> At the moment the elasticsearch integration artifactid is:
>
> hibernate-search-backend-elasticsearch
>
> Elasticsearch is actually more than just a backend (we use this term for
> the jGroups and JMS integration). I think we should rename it to:
>
At the moment the elasticsearch integration artifactid is:
hibernate-search-backend-elasticsearch
Elasticsearch is actually more than just a backend (we use this term for
the jGroups and JMS integration). I think we should rename it to:
hibernate-search-elasticsearch
Thanks,
Davide
___
