Re: Update an Elasticsearch document's array field without using scripting

2015-01-21 Thread Jason Lee
Ah ok, so I don't have to worry about any security risks then if I just use the defaults? On Thursday, January 22, 2015 at 10:50:32 AM UTC+13, Nikolas Everett wrote: > > The current default scripting language, groovy, is sandboxed. If you still > don't want to use it your only option is the get

Re: Update an Elasticsearch document's array field without using scripting

2015-01-21 Thread Nikolas Everett
The current default scripting language, groovy, is sandboxed. If you still don't want to use it your only option is the get update put sequence. On Jan 19, 2015 1:29 PM, "Jason Lee" wrote: > > > I'm trying to add new values to an existing array field in a document. > I've noticed that using the u

Re: Update an Elasticsearch document's array field without using scripting

2015-01-21 Thread Jason Lee
Just another note. A sequence of GET and POST can cause concurrency issues if more than one of our application nodes are communicating with the ES instance, if they try update at the same/similar time, so this is really not ideal. -- You received this message because you are subscribed to the

Update an Elasticsearch document's array field without using scripting

2015-01-19 Thread Jason Lee
I'm trying to add new values to an existing array field in a document. I've noticed that using the update api just overwrites the entire array field. So far all the examples I have found are using scripting but I can't do that because of security. Adding the script in the config/script fol