Hi,
A nice discussion goes here noticed lately
@otis Discovering nodes automatically seems nice,currently it is just a
round robin, I invite you to open an issue
@Ian We did not consider to create another layer on top of Jest, we are now
focused on to complete, clear and maintain it. Also I aggree with Jörg's.
@Jörg You have a point, Jest is a little fat with ES and all Lucene, gonna
check your code base.
Now we are creating a roadmap for Jest, first priority is to complete the
API and remove unnecessary dependencies and code pieces. Then we want to
implement async features.
We want to hear from you guys.
KR,
Ferhat.
On Wednesday, September 26, 2012 6:28:18 PM UTC+3, Jörg Prante wrote:
Hi,
FYI, I am working in my spare time on a modularization of the ES codebase
into client and server code. The client side will have a small footprint
and will offer several protocol implementations, WebSocket, later also
SPDY, and of course REST via HTTP. Also, this Java client will be layered
into ingest, search, and admin client tasks.
Unfortunately it is too early to announce a release with all features
ready, since much of the ES actions have to be implemented yet. A
pre-release for the impatient is available at
GitHub - jprante/elasticsearch-client: Modularized, OpenJDK 11 version of Elasticsearch client
My main motivation was creating a minimal ingest client which is able to
push data into ES while staying compatible to the XContentBuilder API but
without being dependent on the Lucene jars. Using the QueryBuilder API
requires Lucene.
Because of the smaller footprint, an Android ES client might also be
easier to evolve, continuing the effort of
GitHub - karussell/ElasticSearch4Android: ElasticSearch for Android - experiment to get it running ...
But also, this client code can be integrated into such environments you
mention. Personally I think that an integration into Vaadin which uses GWT
would be a good thing, for building pure Java solutions where the ES
cluster is encapsulated in a backend.
Of course, for Javascript ES clients, the more straightforward method is
to set up a proxy to control the access to port 9200 and let jQuery and the
like do their Ajax requests to the ES REST API.
Best regards,
Jörg
On Wednesday, September 26, 2012 4:34:55 PM UTC+2, ian mayo wrote:
Hi,
have you considered the contribution that JEST may make to a GWT
interface for Elasticsearch?
GWT compiles Java to client-side Javascript. On the presumption that
JEST is collating JSON payloads that represent Elasticsearch queries, then
I believe the JSON collation part of the library could be written in a GWT
compliant subset of Java. This subset could then be used by GWT client
applications as an easier way of collating Elasticsearch queries.
Just a thought,
Ian
On Tuesday, 25 September 2012 13:56:36 UTC+1, ferhatsb wrote:
Hi All!
We are proud to announce Jest, a Java client for Elasticsearch rest
interface. GitHub - searchbox-io/Jest: Elasticsearch Java Rest Client.
[...]
All comments, feedbacks are welcomed.
Regards,
Ferhat.
www.searchbox.io
--