7e2696c570
Both top level and inline inner hits are now covered by InnerHitBuilder. Although there are differences between top level and inline inner hits, they now make use of the same builder logic. The parsing of top level inner hits slightly changed to be more readable. Before the nested path or parent/child type had to be specified as encapsuting json object, now these settings are simple fields. Before this was required to allow streaming parsing of inner hits without missing contextual information. Once some issues are fixed with inline inner hits (around multi level hierachy of inner hits), top level inner hits will be deprecated and removed in the next major version. |
||
|---|---|---|
| .. | ||
| community-clients | ||
| groovy-api | ||
| java-api | ||
| perl | ||
| plugins | ||
| python | ||
| reference | ||
| resiliency | ||
| ruby | ||
| README.asciidoc | ||
README.asciidoc
The Elasticsearch docs are in AsciiDoc format and can be built using the Elasticsearch documentation build process See: https://github.com/elastic/docs