wuchong commented on a change in pull request #9008: [FLINK-12942][docs-zh] Translate Elasticsearch Connector page into Ch… URL: https://github.com/apache/flink/pull/9008#discussion_r300869175
########## File path: docs/dev/connectors/elasticsearch.zh.md ########## @@ -410,21 +374,11 @@ input.addSink(new ElasticsearchSink( </div> </div> -The above example will let the sink re-add requests that failed due to -queue capacity saturation and drop requests with malformed documents, without -failing the sink. For all other failures, the sink will fail. If a `ActionRequestFailureHandler` -is not provided to the constructor, the sink will fail for any kind of error. +上面的示例将让 sink 重新添加由于失败而导致的请求队列容量饱和和丢弃请求与格式错误的文档，没有失败了。对于所有其他故障， sink 将失败。如果是 `ActionRequestFailureHandler` 没有提供给构造函数，接收器将因任何类型的错误而失败。 -Note that `onFailure` is called for failures that still occur only after the -`BulkProcessor` internally finishes all backoff retry attempts. -By default, the `BulkProcessor` retries to a maximum of 8 attempts with -an exponential backoff. For more information on the behaviour of the -internal `BulkProcessor` and how to configure it, please see the following section. +请注意，`onFailure` 被调用用于仅在之后仍然发生的故障 `BulkProcessor` 内部完成所有退避重试尝试。默认情况下，`BulkProcessor` 重试最多8次尝试指数退避。有关行为的更多信息内部 `BulkProcessor` 以及如何配置它，请参阅以下部分。 -By default, if a failure handler is not provided, the sink uses a -`NoOpFailureHandler` that simply fails for all kinds of exceptions. The -connector also provides a `RetryRejectedExecutionFailureHandler` implementation -that always re-add requests that have failed due to queue capacity saturation. +默认情况下，如果未提供失败处理程序，则接收器使用a `NoOpFailureHandler` 只是因各种异常而失败。该连接器还提供了 `RetryRejectedExecutionFailureHandler` 实现总是重新添加由于队列容量饱和而失败的请求。 <p style="border-radius: 5px; padding: 5px" class="bg-danger"> <b>IMPORTANT</b>: Re-adding requests back to the internal <b>BulkProcessor</b> Review comment: This sentence is not translated. ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected] With regards, Apache Git Services
