migration #12
Open
migration #12
Conversation
This file contains 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
Littlesqx
reviewed
Sep 30, 2018
| Elasticsearch 6.0 can read indices created in version 5.0 or above. An | ||
| Elasticsearch 6.0 node will not start in the presence of indices created in a | ||
| version of Elasticsearch before 5.0. | ||
| Elasticsearch 6.0 可以读取 2.0 或更高版本创建的索引。如果存在 Elasticsearch 5.0 之前版本创建的索引，Elasticsearch 6.0 节点将不能启动。 |
There was a problem hiding this comment.
Elasticsearch 6.0 可以读取 5.0 或更高版本创建的索引。
|
|
||
| ==== `InternalStats` and `Stats` getCountAsString() method removed | ||
| ==== 移除 `InternalStats` 和 `Stats` getCountAsString() 方法 |
There was a problem hiding this comment.
移除 InternalStats 和 Stats 的 getCountAsString() 方法
|
|
||
| The filter aggregation classes were moved to `org.elasticsearch.search.aggregations.bucket.filter` | ||
| 过滤器聚合类移动至 `org.elasticsearch.search.aggregations.bucket.filter` 。 |
There was a problem hiding this comment.
这句话。前面加了空格，然而上面一行却没有加。 如果不加，那上面和其他文件的地方也需要统一。
参考 中文文案排版指北
| 现在需要将所要求的等级作为非 null 、非空 double 数据传至构建器构造函数中，而不是通过构建器的 setter 配置。setter `values()` 方法也相应的移除了。 |
|
|
||
| * The container an azure repository is configured with will no longer be created automatically. | ||
| It must exist before the azure repository is created. | ||
| * azure 仓库配置的容器不会自动创建。它必须在 azure 仓库之前创建。 |
There was a problem hiding this comment.
这句话不是很理解。字面翻译是 配置了 azure 仓库的容器不会被自动创建。它必须在 azure 仓库被创建前就存在。但是意思读不通。
| The `base` similarity is now ignored as coords and query normalization have | ||
| been removed. If provided, this setting will be ignored and issue a | ||
| deprecation warning. | ||
| 因为 coords 和查询标准化已移除使得 `base` 相似性现在会被忽略。 如果提供，这个设置会被忽略并会产生一个过期警告。 | ||
|
|
| upgrading from a previous version of Elasticsearch and preserve your existing | ||
| <<jvm-options,`jvm.options`>>, you should add the following GC logging settings | ||
| so that this valuable debugging information is available: | ||
| === All permission bootstrap 校验 |
|
|
||
| === GC 日志 | ||
|
|
||
| 从 Elasticsearch 6.2.0 开始，JVM <<gc-logging,GC 日志>> 已启用。这种轻量级设置可以深入探究 GC 问题。 这些设置通过 <<jvm-options,`jvm.options`>> 设置， |
|
|
||
| ==== Remove support for elasticsearch.json and elasticsearch.yaml configuration file | ||
| ==== 移除对 elasticsearch.json 和 elasticsearch.yaml 配置文件地支持 |
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.
Breaking changes 章节翻译初版