If I have a document I’m storing that looks like this:
doc = {
userId: *‘*yoyomamma',
physicians: [{
name: sanjay gupta,
id: 403494
},
{
name: daniel litvak,
id: 3382
}],
procedures: [{
name: appendectomy,
id: 3939,
date: 2/3/2012
}
… etc a
it at one time. We plan to start stress testing the
system soon.
Cheers
Jack
On Fri, Dec 26, 2014 at 9:55 AM, phil swenson phil.swen...@gmail.com
wrote:
no answer, so let me ask a different way. how are most of the es
javascript client apps managing the instance of the client?
do you have
something like
https://github.com/coopernurse/node-pool ?
Thanks for any comments!
phil
On Wed, Dec 24, 2014 at 10:34 AM, Phil Swenson phil.swen...@gmail.com
wrote:
I'm writing a node/es app using the es javascript api
Is there any reason to use pooling for all the javascript clients
I'm writing a node/es app using the es javascript api
Is there any reason to use pooling for all the javascript clients? Or
should I just use one client for the app?
Thanks,
phil
--
You received this message because you are subscribed to the Google Groups
elasticsearch group.
To
did you ever find an answer to this question?
On Thursday, November 6, 2014 7:17:36 PM UTC-7, Alexandre Rafalovitch wrote:
ElasticSearch 1.4 is out and I can't see any mentions that Rivers are
deprecated.
Has that (informal) decision been reversed? Or was the timeline
further out?
