File: has-parent-query.asciidoc

package info (click to toggle)
elasticsearch 1.0.3%2Bdfsg-5
  • links: PTS, VCS
  • area: main
  • in suites: jessie-kfreebsd
  • size: 37,220 kB
  • sloc: java: 365,486; xml: 1,258; sh: 714; python: 505; ruby: 354; perl: 134; makefile: 41
file content (57 lines) | stat: -rw-r--r-- 1,662 bytes parent folder | download
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-parent-query]]
=== Has Parent Query

The `has_parent` query works the same as the
<<query-dsl-has-parent-filter,has_parent>>
filter, by automatically wrapping the filter with a constant_score (when
using the default score type). It has the same syntax as the
<<query-dsl-has-parent-filter,has_parent>>
filter. 

[source,js]
--------------------------------------------------
{
    "has_parent" : {
        "parent_type" : "blog",
        "query" : {
            "term" : {
                "tag" : "something"
            }
        }
    }
}
--------------------------------------------------

[float]
==== Scoring capabilities

The `has_parent` also has scoring support. The
supported score types are `score` or `none`. The default is `none` and
this ignores the score from the parent document. The score is in this
case equal to the boost on the `has_parent` query (Defaults to 1). If
the score type is set to `score`, then the score of the matching parent
document is aggregated into the child documents belonging to the
matching parent document. The score type can be specified with the
`score_type` field inside the `has_parent` query:

[source,js]
--------------------------------------------------
{
    "has_parent" : {
        "parent_type" : "blog",
        "score_type" : "score",
        "query" : {
            "term" : {
                "tag" : "something"
            }
        }
    }
}
--------------------------------------------------

[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.