There is a "local" mode [1]. In this mode you start up the single embedded node and use the client from that node [2], which will bypass networking but responses are still serialized to bytes [3].
[1] http://www.elastic.co/guide/en/elasticsearch/client/java-api/current/client.html#node-client [2] https://github.com/elastic/elasticsearch/blob/master/src/main/java/org/elasticsearch/node/Node.java#L223 [3] https://github.com/elastic/elasticsearch/blob/master/src/main/java/org/elasticsearch/transport/local/LocalTransport.java On Sunday, April 12, 2015 at 11:07:31 PM UTC-4, Ted Smith wrote: > > Hello: > > I am running ES with one Node, one Shard in embedded Java app. > Does Node client run in "true" embedded mode or is it still going > through the client server data flow? > > If I create a Search Request, object and excute it, get it, > would ES first serialize it into Json data and send to a server thread > which would deserialize it, and then get result, convert it to Json > and send back to client, which would convert it into java object? > > I'd expect in "true" embedded mode, the search object and result object > would be directly pass in and out, without the overhead of client-server > mode, > which could be huge performance gain. > > Thanks > > > -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/1cca84a4-6b1c-4ba0-96dd-b4e6ec778523%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
