leslie-tsang commented on a change in pull request #6415:
URL: https://github.com/apache/apisix/pull/6415#discussion_r815010695



##########
File path: docs/zh/latest/plugins/http-logger.md
##########
@@ -44,16 +46,13 @@ title: http-logger
 | auth_header      | string  | 可选   | ""            |         | 授权头部。          
                          |
 | timeout          | integer | 可选   | 3             | [1,...] | 
发送请求后保持连接活动的时间。                   |
 | name             | string  | 可选   | "http logger" |         | 标识 logger 
的唯一标识符。                     |
-| batch_max_size   | integer | 可选   | 1000          | [1,...] | 
设置每批发送日志的最大条数,当日志条数达到设置的最大值时,会自动推送全部日志到 `HTTP/HTTPS` 服务。 |
-| inactive_timeout | integer | 可选   | 5             | [1,...] | 
刷新缓冲区的最大时间(以秒为单位),当达到最大的刷新时间时,无论缓冲区中的日志数量是否达到设置的最大条数,也会自动将全部日志推送到 `HTTP/HTTPS` 
服务。 |
-| buffer_duration  | integer | 可选   | 60            | [1,...] | 
必须先处理批次中最旧条目的最长期限(以秒为单位)。   |
-| max_retry_count  | integer | 可选   | 0             | [0,...] | 
从处理管道中移除之前的最大重试次数。               |
-| retry_delay      | integer | 可选   | 1             | [0,...] | 
如果执行失败,则应延迟执行流程的秒数。             |
 | include_req_body | boolean | 可选   | false         | [false, true] | 是否包括请求 
body。false: 表示不包含请求的 body ; true: 表示包含请求的 body 。 |
 | include_resp_body| boolean | 可选   | false         | [false, true] | 
是否包括响应体。包含响应体,当为`true`。 |
 | include_resp_body_expr | array  | 可选    |           |         | 是否采集响体, 
基于[lua-resty-expr](https://github.com/api7/lua-resty-expr)。 该选项需要开启 
`include_resp_body`|
 | concat_method    | string  | 可选   | "json"        | ["json", "new_line"] | 
枚举类型: `json`、`new_line`。**json**: 对所有待发日志使用 `json.encode` 编码。**new_line**: 
对每一条待发日志单独使用 `json.encode` 编码并使用 "\n" 连接起来。 |
 
+事实上,我们还有一些公共参数交由批处本插件支持使用批处理器来聚合条目(日志数据),并批量处理它们。这样可以减少每个时间范围内从插件发送的请求数。当然本插件提供默认的批处理器配置,因此您不必担心会有额外的问题。如果你想了解有关批处理器相关参数的更多信息,请参考
 [Batch-Processor](../batch-processor.md#配置) 配置部分。

Review comment:
       The content of the translation needs to be more <ins>accurate</ins> and 
<ins>fluent</ins>. :)

##########
File path: docs/en/latest/batch-processor.md
##########
@@ -30,14 +30,13 @@ than 1 will start aggregating the entries until it reaches 
the max size or the t
 The only mandatory parameter to create a batch processor is a function. The 
function will be executed when the batch reaches the max size
 or when the buffer duration exceeds.
 
-|Name           |Requirement    |Description|
-|-------        |-----          |------|
-|name           |optional       |A unique identifier to identity the batch 
processor|
-|batch_max_size |optional       |Max size of each batch, default is 1000|
-|inactive_timeout|optional      |maximum age in seconds when the buffer will 
be flushed if inactive, default is 5s|
-|buffer_duration|optional       |Maximum age in seconds of the oldest entry in 
a batch before the batch must be processed, default is 5|
-|max_retry_count|optional       |Maximum number of retries before removing 
from the processing pipe line; default is zero|
-|retry_delay    |optional       |Number of seconds the process execution 
should be delayed if the execution fails; default is 1|
+| Name             | Type    | Requirement | Default | Valid   | Description   
                                               |
+| ---------------- | ------- | ----------- | ------- | ------- | 
------------------------------------------------------------ |
+| batch_max_size   | integer | optional    | 1000    | [1,...] | Sets the 
maximum number of logs sent in each batch. When the number of logs reaches the 
set maximum, all logs will be automatically pushed to the HTTP/HTTPS service. |

Review comment:
       Why we remove `name` attr desc here ?




-- 
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.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


Reply via email to