Painlessスクリプト利用時の想定外の挙動

[junkoshimane]

• 参考

ElasticSearch Painless script: How to iterate in an array of Nested Objects

Painless: problem accessing nested object using dot notation

Hi, I'm having problems reindexing data using a painless script. The nested field context.data.result is mapped as an object in the destination index, but in some cases the source data is either a string or an array of longs The script attempts to: Check if the field exists Check the field's type If it is a string or array create a temporary string / array variable assign the value of the offending field to this variable change the value of the field to be a new object (passed in via param…

Painless access to nested objects

Hi, I'm facing the following situation : My data has a structure similar to this { "site1" : { "events": [ {"event1", "date1"}, {"event1","date1-2"},{"event2","date3"}}] ... }, "site2" : { "events": [ {"event2", "date4"}, {"event1","date5"},{"event3","date6}}] ... }, ... } What I want is : Count the number of sites where a specific event occurs during a given time range. Count for each site the numer of occurences during a specific time range. I could get the first via a simple …

Get nested fields data with Painless scripting

I'm trying to access nested fields data through Painless inline scripting and can't seem to be able to get it to work. Without getting into too many details, the reason for this is that we have certain fields that support a default value, and an optional custom override. To avoid having to return both fields and then have the application decide which one to use, I'd like to use a scripted field to check if the override has value and return that, or otherwise fallback to the default value. I've …

Use normal and nested fields in same Painless script query?

I have a mapping like this: { printings: { type: "nested", properties: { prop1: {type: "number"} } }, prop2: {type: "number"} } I then want to build a Painless query like this: "script": { "lang": "painless", "inline": "doc['prop1'] > (3 * doc['printings.prop2'])" } However testing this in Sense doesn't work. If I replace the nested prop2 with a simple number then it does work. Is there a way to access both root and nested props in a sin…