elasticsearch - comparing a nested field with another field in the document

In the case of the nested search, you are searching the nested objects without the parent. Unfortunately, there is no hidden join that you can apply with nested objects.

At least currently, that means you do not receive both the "parent" and the nested document in the script. You can confirm this by replacing your script with both of these and testing the result:

# Parent Document does not exist"script": {  "script": "doc['primary_content_type_id'].value == 12"}# Nested Document should exist"script": {  "script": "doc['content.content_type_id'].value == 12"}

You could do this in a performance-inferior way by looping across objects (rather than inherently having ES do this for you with nested). This means that you would have to reindex your documents and nested documents as a single document for this to work. Considering the way that you are trying to use it, this probably wouldn't be too different and it may even perform better (especially given the lack of an alternative).

# This assumes that your default scripting language is Groovy (default in 1.4)# Note1: "find" will loop across all of the values, but it will#  appropriately short circuit if it finds any!# Note2: It would be preferable to use doc throughout, but since we need the#  arrays (plural!) to be in the _same_ order, then we need to parse the#  _source. This inherently means that you must _store_ the _source, which#  is the default. Parsing the _source only happens on the first touch."script": {  "script": "_source.content.find { it.content_type_id == _source.primary_content_type_id && ! it.assigned } != null",  "_cache" : true}

I cached the result because nothing dynamic is occurring here (e.g., not comparing dates to now for instance), so it's pretty safe to cache, thereby making future lookups much faster. Most filters are cached by default, but scripts are one of the few exceptions.

Since it must compare both values to be sure that it found the correct inner object, you are duplicating some amount of work, but it's practically unavoidable. Having the term filter is most likely going to be superior to just doing this check without it.