blob: 1a8e1161ee4326e85d1667195cb80f76ee865522 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
|
[[query-dsl-has-child-filter]]
=== Has Child Filter
The `has_child` filter accepts a query and the child type to run
against, and results in parent documents that have child docs matching
the query. Here is an example:
[source,js]
--------------------------------------------------
{
"has_child" : {
"type" : "blog_tag",
"query" : {
"term" : {
"tag" : "something"
}
}
}
}
--------------------------------------------------
The `type` is the child type to query against. The parent type to return
is automatically detected based on the mappings.
The way that the filter is implemented is by first running the child
query, doing the matching up to the parent doc for each document
matched.
The `has_child` filter also accepts a filter instead of a query:
[source,js]
--------------------------------------------------
{
"has_child" : {
"type" : "comment",
"filter" : {
"term" : {
"user" : "john"
}
}
}
}
--------------------------------------------------
[float]
==== Memory Considerations
With the current implementation, all `_id` values are loaded to memory
(heap) in order to support fast lookups, so make sure there is enough
memory for it.
[float]
==== Caching
The `has_child` filter cannot be cached in the filter cache. The `_cache`
and `_cache_key` options are a no-op in this filter. Also any filter that
wraps the `has_child` filter either directly or indirectly will not be cached.
|
