Skip to content

Commit bcff42d

Browse files
committed
修改,第二次提交
1 parent a5d8b47 commit bcff42d

File tree

1 file changed

+22
-39
lines changed

1 file changed

+22
-39
lines changed

400_Relationships/22_Top_hits.asciidoc

Lines changed: 22 additions & 39 deletions
Original file line numberDiff line numberDiff line change
@@ -1,12 +1,8 @@
11
[[top-hits]]
2-
=== Field Collapsing
2+
=== 字段折叠
33

4-
A common requirement is the need to present search results grouped by a particular
5-
field. ((("field collapsing")))((("relationships", "field collapsing")))We might want to return the most relevant blog posts _grouped_ by the
6-
user's name. ((("terms aggregation")))((("aggregations", "field collapsing"))) Grouping by name implies the need for a `terms` aggregation. To
7-
be able to group on the user's _whole_ name, the name field should be
8-
available in its original `not_analyzed` form, as explained in
9-
<<aggregations-and-analysis>>:
4+
一个普遍的需求是需要通过特定字段进行分组。例如我们需要按照用户名称 _分组_ 返回最相关的博客文章。((("terms aggregation")))((("aggregations", "field collapsing")))
5+
按照用户名分组意味着进行 `terms` 聚合。为能够按照用户 _整体_ 名称进行分组,名称字段应保持 `not_analyzed` 的形式,具体说明参考 <<aggregations-and-analysis>>:
106

117
[source,json]
128
--------------------------------
@@ -29,11 +25,11 @@ PUT /my_index/_mapping/blogpost
2925
}
3026
}
3127
--------------------------------
32-
<1> The `user.name` field will be used for full-text search.
33-
<2> The `user.name.raw` field will be used for grouping with the `terms`
34-
aggregation.
28+
<1> `user.name` 字段将用来进行全文检索。
29+
<2> `user.name.raw` 字段将用来通过 `terms` 聚合进行分组。
3530

36-
Then add some data:
31+
32+
然后添加一些数据:
3733

3834
[source,json]
3935
--------------------------------
@@ -72,13 +68,12 @@ PUT /my_index/blogpost/4
7268
}
7369
--------------------------------
7470

75-
Now we can run a query looking for blog posts about `relationships`, by users
76-
called `John`, and group the results by user, thanks to the
77-
{ref}/search-aggregations-metrics-top-hits-aggregation.html[`top_hits` aggregation]:
71+
现在我们执行一个查询,来查找标题包含 `relationships` 并且作者名包含 `John` 的博客,查询结果再按作者名分组,感谢 {ref}/search-aggregations-metrics-top-hits-aggregation.html[`top_hits` aggregation]
72+
提供了按照用户进行分组的功能:
7873

7974
[source,json]
8075
--------------------------------
81-
GET /my_index/blogpost/_search
76+
GET /my_index/blogpost/_search
8277
{
8378
"size" : 0, <1>
8479
"query": { <2>
@@ -103,17 +98,13 @@ GET /my_index/blogpost/_search
10398
}
10499
}
105100
--------------------------------
106-
<1> The blog posts that we are interested in are returned under the
107-
`blogposts` aggregation, so we can disable the usual search `hits` by
108-
setting the `size` to 0.
109-
<2> The `query` returns blog posts about `relationships` by users named `John`.
110-
<3> The `terms` aggregation creates a bucket for each `user.name.raw` value.
111-
<4> The `top_score` aggregation orders the terms in the `users` aggregation
112-
by the top-scoring document in each bucket.
113-
<5> The `top_hits` aggregation returns just the `title` field of the five most
114-
relevant blog posts for each user.
101+
<1> 我们感兴趣的博客文章是通过 `blogposts` 聚合返回的,所以我们可以通过将 `size` 设置成0来禁止 `hits` 常规搜索。
102+
<2> `query` 返回通过 `relationships` 查找名称为 `John` 的用户的博客文章。
103+
<3> `terms` 聚合为每一个 `user.name.raw` 创建一个桶。
104+
<4> `top_score` 聚合对通过 `users` 聚合得到的每一个桶按照文档评分对词项进行排序。
105+
<5> `top_hits` 聚合仅为每个用户返回五个最相关的博客文章的 `title` 字段。
115106

116-
The abbreviated response is shown here:
107+
这里显示简短响应结果:
117108

118109
[source,json]
119110
--------------------------------
@@ -152,19 +143,11 @@ The abbreviated response is shown here:
152143
},
153144
...
154145
--------------------------------
155-
<1> The `hits` array is empty because we set `size` to 0.
156-
<2> There is a bucket for each user who appeared in the top results.
157-
<3> Under each user bucket there is a `blogposts.hits` array containing
158-
the top results for that user.
159-
<4> The user buckets are sorted by the user's most relevant blog post.
160-
161-
Using the `top_hits` aggregation is the((("top_hits aggregation"))) equivalent of running a query to
162-
return the names of the users with the most relevant blog posts, and then running
163-
the same query for each user, to get their best blog posts. But it is much more
164-
efficient.
146+
<1> 因为我们设置 `size` 为0,所以 `hits` 数组是空的。
147+
<2> 在顶层查询结果中出现的每一个用户都会有一个对应的桶。
148+
<3> 在每个用户桶下面都会有一个 `blogposts.hits` 数组包含针对这个用户的顶层查询结果。
149+
<4> 用户桶按照每个用户最相关的博客文章进行排序。
165150

166-
The top hits returned in each bucket are the result of running a light
167-
_mini-query_ based on the original main query. The mini-query supports the
168-
usual features that you would expect from search such as highlighting and
169-
pagination.
151+
使用 `top_hits` 聚合((("top_hits aggregation")))等效运行一个查询返回这些用户的名字和他们最相关的博客文章,然后为每一个用户运行相同的查询,以获得最好的博客。但前者的效率要好很多。
170152

153+
每一个桶返回的顶层查询命中结果是基于最初主查询进行的一个轻量 _迷你查询_ 结果集。这个迷你查询提供了一些你期望的常用特性例如高亮显示以及分页功能。

0 commit comments

Comments
 (0)