|
|
@@ -14,7 +14,7 @@ The `reverse_nested` aggregation must be defined inside a `nested` aggregation.
|
|
|
which means that it joins back to the root / main document level. The path cannot contain a reference to
|
|
|
a nested object field that falls outside the `nested` aggregation's nested structure a `reverse_nested` is in.
|
|
|
|
|
|
-For example, lets say we have an index for a ticket system which issues and comments. The comments are inlined into
|
|
|
+For example, lets say we have an index for a ticket system with issues and comments. The comments are inlined into
|
|
|
the issue documents as nested documents. The mapping could look like:
|
|
|
|
|
|
[source,js]
|
|
|
@@ -40,7 +40,7 @@ the issue documents as nested documents. The mapping could look like:
|
|
|
<1> The `comments` is an array that holds nested documents under the `issue` object.
|
|
|
|
|
|
The following aggregations will return the top commenters' username that have commented and per top commenter the top
|
|
|
-tags that issues have the commenter has commented to:
|
|
|
+tags of the issues the user has commented on:
|
|
|
|
|
|
[source,js]
|
|
|
--------------------------------------------------
|
smayzak