chapter10_part8:/070_Index_Mgmt/32_Metadata_all.asciidoc #300
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
leo650
reviewed
Sep 19, 2016
| indexes the ((("metadata, document", "_all field")))((("_all field", sortas="all field")))values from all other fields as one big string. The `query_string` | ||
| query clause (and searches performed as `?q=john`) defaults to searching in | ||
| the `_all` field if no other field is specified. | ||
| 在 <<search-lite>> 中，我们介绍了 `_all` 字段：一个索引所有字段((("metadata, document", "_all field")))((("_all field", sortas="all field")))作为一个大字段的特殊字段。 `query_string` |
There was a problem hiding this comment.
- a special field that indexes the values from all other fields as one big string. 不知道翻译成“一个把其它字段值当作一个大字符串来索引的特殊字段”会不会好一点。【仅供参考】
leo650
reviewed
Sep 19, 2016
| analyzer has been set on the fields where the values originate. And | ||
| like any `string` field, you can configure which analyzer the `_all` | ||
| field should use: | ||
| 记住，`_all` 字段仅仅是一个((("analyzers", "configuring for all field"))) 进过分析的 `string` 字段。它使用默认分词器来分析它的值，不管这个值原本所在字段指定的分词器。就像所有 `string` 字段，你可以配置 `_all` 字段使用的分词器： |
There was a problem hiding this comment.
an analyzed string field：一个分词的 string 字段？
leo650
reviewed
Sep 19, 2016
| `title`, `overview`, `summary`, and `tags`. Instead of disabling the `_all` | ||
| field completely, disable `include_in_all` for all fields by default, | ||
| and enable it only on the fields you choose: | ||
| 你可能想要保留 `_all` 字段作为一个全文字段，例如 `title`，`overview`，`summary` 和 `tags`。 相对于完成禁用 `_all` 字段，你可以为所有字段默认禁用 `include_in_all` 选项，仅在你选择的字段上启用： |
|
LGTM |
tangmisi
reviewed
Oct 13, 2016
| is a shotgun approach to search. By querying individual fields, you have more | ||
| flexbility, power, and fine-grained control over which results are considered | ||
| to be most relevant. | ||
| 随着应用的发展，搜索需求变得更加明确，你会发现自己使用 `_all` 字段越来越少。 `_all` 字段是搜索的应急之策。通过查询指定字段，你可以更加灵活，强大和精准的控制搜索结果，提高相关性。 |
There was a problem hiding this comment.
使用 _all 字段越来越少 -->越来越少使用_all 字段；“你可以更加灵活，强大和精准的控制搜索结果，提高相关性。”这么理解好像也没错，但我个人觉得翻译成"你的查询更加灵活、强大，你也可以对相关性最高的搜索结果进行更细粒度的控制"比较符合原意。你斟酌一下吧，不是必改~
tangmisi
reviewed
Oct 13, 2016
| `title`, `overview`, `summary`, and `tags`. Instead of disabling the `_all` | ||
| field completely, disable `include_in_all` for all fields by default, | ||
| and enable it only on the fields you choose: | ||
| 你可能想要保留 `_all` 字段作为一个全文字段，例如 `title`，`overview`，`summary` 和 `tags`。 相对于完全禁用 `_all` 字段，你可以为所有字段默认禁用 `include_in_all` 选项，仅在你选择的字段上启用： |
There was a problem hiding this comment.
你可能想要保留 _all 字段作为一个全文字段，例如 title，overview，summary 和 tags。-->你可能想要保留 _all 字段作为一个只包含某些特定字段的全文字段，例如只包含 title，overview，summary 和 tags。；
tangmisi
reviewed
Oct 13, 2016
| analyzer has been set on the fields where the values originate. And | ||
| like any `string` field, you can configure which analyzer the `_all` | ||
| field should use: | ||
| 记住，`_all` 字段仅仅是一个((("analyzers", "configuring for all field"))) 进过分词的 `string` 字段。它使用默认分词器来分析它的值，不管这个值原本所在字段指定的分词器。就像所有 `string` 字段，你可以配置 `_all` 字段使用的分词器： |
|
LGTM |
|
LGTM |
tangmisi
pushed a commit
to tangmisi/elasticsearch-definitive-guide
that referenced
this pull request
Oct 31, 2016
…ch-cn#300) * chapter10_part8:/070_Index_Mgmt/32_Metadata_all.asciidoc * review后修改 * 二次review后修改
|
@candythinking 已经 merge 的不用 review 了，主要是open 的 pr 啦 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.