docs: merge released change logs (v5.0.14)
This commit is contained in:
Zaiming (Stone) Shi
parent
a7fc5e8fe1
commit
10bbf97e03
|
|
@ -2,8 +2,6 @@
|
|||
|
||||
## Enhancements
|
||||
|
||||
- [#8329](https://github.com/emqx/emqx/pull/8329) The MongoDB library has been upgraded to support MongoDB 5.1+
|
||||
|
||||
- [#9593](https://github.com/emqx/emqx/pull/9593) Obfuscated sensitive data in the response when querying `bridges` information by API.
|
||||
|
||||
- [#9614](https://github.com/emqx/emqx/pull/9614) Make possible to configure `host:port` from environment variables without quotes.
|
||||
|
|
@ -20,14 +18,14 @@
|
|||
- [#9675](https://github.com/emqx/emqx/pull/9675) HTTP client library `ehttpc` upgraded from `0.4.2` to `0.4.3`.
|
||||
Library `eredis_cluster` which manages clients to redis clusters upgraded from `0.7.1` to `0.7.5`.
|
||||
|
||||
- [#9691](https://github.com/emqx/emqx/pull/9691) The MongoDB library has been upgraded to support MongoDB 5.1+
|
||||
|
||||
- [#9713](https://github.com/emqx/emqx/pull/9713) Introduce `api_key.bootstrap_file` to initialize the api key at boot time.
|
||||
Deprecate `dashboard.bootstrap_users_file`.
|
||||
Limit the maximum number of api keys to 100 instead of 30.
|
||||
|
||||
## Bug fixes
|
||||
|
||||
- [#8648](https://github.com/emqx/emqx/pull/8648) When deleting a non-existing bridge the server gave a success response. This has been fixed so that the server instead gives an error response when the user attempts to delete a non-existing bridge.
|
||||
|
||||
- [#9637](https://github.com/emqx/emqx/pull/9637) Fix the expiry_interval fields of the clients HTTP API to measure in seconds.
|
||||
|
||||
- [#9638](https://github.com/emqx/emqx/pull/9638) Fix the problem of data loss and bad match when the MySQL driver is disconnected.
|
||||
|
|
@ -40,6 +38,10 @@
|
|||
|
||||
- [#9667](https://github.com/emqx/emqx/pull/9667) Remove possibility to set `clientid` for `/publish` and `/publish/bulk` HTTP APIs. This is to reduce the risk for security confusion.
|
||||
|
||||
- [#9672](https://github.com/emqx/emqx/pull/9672) Fix the problem that the bridge is not available when the Payload template is empty in the MQTT bridge.
|
||||
|
||||
- [#9678](https://github.com/emqx/emqx/pull/9678) When deleting a non-existing bridge the server gave a success response. This has been fixed so that the server instead gives an error response when the user attempts to delete a non-existing bridge.
|
||||
|
||||
- [#9687](https://github.com/emqx/emqx/pull/9687) Fix the problem that sending messages to data-bridges failed because of incorrect handling of some data-bridges without `local_topic` field configured.
|
||||
Before this change, if some bridges have configured the `local_topic` field but others have not, a `function_clause` error will occur when forwarding messages to the data-bridges.
|
||||
|
||||
|
|
@ -66,3 +68,5 @@
|
|||
- [#9716](https://github.com/emqx/emqx/pull/9716) MQTT bridge config compatibility fix. The config created from before v5.0.12 may encounter a compatibility issue after upgraded to v5.0.13.
|
||||
|
||||
- [#9717](https://github.com/emqx/emqx/pull/9717) Prior to this fix, if it always times out when trying to connect a bridge server, it's not possible to change other configs even when the bridge is disabled.
|
||||
|
||||
- [#9730](https://github.com/emqx/emqx/pull/9730) Potential leaks of atoms that could lead to a crash if a lot of resources were created have been removed.
|
||||
|
|
|
|||
|
|
@ -2,8 +2,6 @@
|
|||
|
||||
## 增强
|
||||
|
||||
- [#8329](https://github.com/emqx/emqx/pull/8329) MongoDB 的驱动现在已经升级到 MongoDB 5.1+ 了。
|
||||
|
||||
- [#9593](https://github.com/emqx/emqx/pull/9593) 通过 API 查询 `bridges` 信息时将混淆响应中的敏感数据。
|
||||
|
||||
- [#9614](https://github.com/emqx/emqx/pull/9614) 允许环境变量重载 `host:port` 值时不使用引号。
|
||||
|
|
@ -20,14 +18,14 @@
|
|||
- [#9675](https://github.com/emqx/emqx/pull/9675) HTTP 客户端库 `ehttpc` 从 `0.4.2` 升级到 `0.4.3`
|
||||
Redis cluster 客户端库 `eredis_cluster` 从 `0.7.1` 升级到 `0.7.5`.
|
||||
|
||||
- [#9691](https://github.com/emqx/emqx/pull/9691) MongoDB 的驱动现在已经升级到 MongoDB 5.1+ 了。
|
||||
|
||||
- [#9713](https://github.com/emqx/emqx/pull/9713) 引入 `api_key.bootstrap_file`，用于启动时初始化api密钥。
|
||||
废弃 `dashboard.boostrap_users_file`。
|
||||
将 API 密钥的最大数量限制提升为 100（原来为30）。
|
||||
|
||||
## 修复
|
||||
|
||||
- [#8648](https://github.com/emqx/emqx/pull/8648) 修复了当通过 API 删除一个不存在的桥接时，服务器会返回操作成功的问题，现在将会返回操作失败的信息。
|
||||
|
||||
- [#9637](https://github.com/emqx/emqx/pull/9637) 修复 clients HTTP API 下的 expiry_interval 字段的时间单位为秒。
|
||||
|
||||
- [#9638](https://github.com/emqx/emqx/pull/9638) 修复 MySQL 驱动断开连接时出现的数据丢失和匹配错误的问题。
|
||||
|
|
@ -40,6 +38,10 @@
|
|||
|
||||
- [#9667](https://github.com/emqx/emqx/pull/9667) 从 HTTP API /publish 和 /publish/bulk 中移除 clientid, 降低安全风险
|
||||
|
||||
- [#9672](https://github.com/emqx/emqx/pull/9672) 修复 MQTT 桥接中 Payload 模板为空时桥接不可用的问题。
|
||||
|
||||
- [#9678](https://github.com/emqx/emqx/pull/9678) 修复了当通过 API 删除一个不存在的桥接时，服务器会返回操作成功的问题，现在将会返回操作失败的信息。
|
||||
|
||||
- [#9687](https://github.com/emqx/emqx/pull/9687) 修复由于某些数据桥接未配置 `local_topic` 字段，导致的所有数据桥接无法发送消息。
|
||||
在此改动之前，如果有些桥接设置了 `local_topic` 字段而有些没有设置，数据桥接转发消息时会出现 `function_clause` 的错误。
|
||||
|
||||
|
|
@ -62,3 +64,5 @@
|
|||
- [#9716](https://github.com/emqx/emqx/pull/9716) 修复 v5.0.12 之前的 MQTT 桥接配置在 升级到 v5.0.13 后 HTTP API 查询 桥接配置时的一个兼容性问题。
|
||||
|
||||
- [#9717](https://github.com/emqx/emqx/pull/9717) 修复已禁用的桥接资源服务器连接超时的情况下不能修改其他配置参数的问题。
|
||||
|
||||
- [#9730](https://github.com/emqx/emqx/pull/9730) 如果创建了大量的资源，可能会导致崩溃的潜在的原子泄漏已经被删除。
|
||||
|
|
|
|||
|
|
@ -1 +0,0 @@
|
|||
Obfuscated sensitive data in the response when querying `bridges` information by API.
|
||||
|
|
@ -1 +0,0 @@
|
|||
通过 API 查询 `bridges` 信息时将混淆响应中的敏感数据。
|
||||
|
|
@ -1,4 +0,0 @@
|
|||
Make possible to configure `host:port` from environment variables without quotes.
|
||||
Prior to this change, when overriding a `host:port` config value from environment variable, one has to quote it as:
|
||||
`env EMQX_BRIDGES__MQTT__XYZ__SERVER='"localhost:1883"'`.
|
||||
Now it's possible to set it without quote as `env EMQX_BRIDGES__MQTT__XYZ__SERVER='localhost:1883'`.
|
||||
|
|
@ -1,4 +0,0 @@
|
|||
允许环境变量重载 `host:port` 值时不使用引号。
|
||||
在此修复前，环境变量中使用 `host:port` 这种配置时，用户必须使用引号，例如：
|
||||
`env EMQX_BRIDGES__MQTT__XYZ__SERVER='"localhost:1883"'`。
|
||||
此修复后，可以不使用引号，例如 `env EMQX_BRIDGES__MQTT__XYZ__SERVER='localhost:1883'`。
|
||||
|
|
@ -1 +0,0 @@
|
|||
Deprecates `enable_batch` and `enable_queue` options for bridges/resources. After this change, queuing is always enabled for bridges, and batching is controlled by the `batch_size` option: `batch_size > 1` means batching will be enabled.
|
||||
|
|
@ -1 +0,0 @@
|
|||
废弃了桥接的 `enable_batch` 和 `enable_queue` 配置项 。在这一改变之后，桥接的工作进程总是启用缓存队列，而批处理由 `batch_size` 选项控制：`batch_size > 1` 则意味着启用批处理。
|
||||
|
|
@ -1 +0,0 @@
|
|||
Implement sliding window average metrics.
|
||||
|
|
@ -1 +0,0 @@
|
|||
实施滑动窗口平均度量。
|
||||
|
|
@ -1 +0,0 @@
|
|||
Made rule engine behavior more consistent with bridge behavior regarding metrics: if a rule engine is disabled, its metrics are now reset
|
||||
|
|
@ -1 +0,0 @@
|
|||
使得规则引擎的行为与桥梁的指标行为更加一致：如果一个规则引擎被禁用，其指标现在会被重置。
|
||||
|
|
@ -1,2 +0,0 @@
|
|||
HTTP client library `ehttpc` upgraded from `0.4.2` to `0.4.3`.
|
||||
Library `eredis_cluster` which manages clients to redis clusters upgraded from `0.7.1` to `0.7.5`.
|
||||
|
|
@ -1,2 +0,0 @@
|
|||
HTTP 客户端库 `ehttpc` 从 `0.4.2` 升级到 `0.4.3`
|
||||
Redis cluster 客户端库 `eredis_cluster` 从 `0.7.1` 升级到 `0.7.5`.
|
||||
|
|
@ -1 +0,0 @@
|
|||
The MongoDB library has been upgraded to support MongoDB 5.1+
|
||||
|
|
@ -1 +0,0 @@
|
|||
MongoDB 的驱动现在已经升级到 MongoDB 5.1+ 了。
|
||||
|
|
@ -1,3 +0,0 @@
|
|||
Introduce `api_key.bootstrap_file` to initialize the api key at boot time.
|
||||
Deprecate `dashboard.bootstrap_users_file`.
|
||||
Limit the maximum number of api keys to 100 instead of 30.
|
||||
|
|
@ -1,3 +0,0 @@
|
|||
引入 `api_key.bootstrap_file`，用于启动时初始化api密钥。
|
||||
废弃 `dashboard.boostrap_users_file`。
|
||||
将 API 密钥的最大数量限制提升为 100（原来为30）。
|
||||
|
|
@ -1 +0,0 @@
|
|||
Fix the expiry_interval fields of the clients HTTP API to measure in seconds.
|
||||
|
|
@ -1 +0,0 @@
|
|||
修复 clients HTTP API 下的 expiry_interval 字段的时间单位为秒。
|
||||
|
|
@ -1 +0,0 @@
|
|||
Fix the problem of data loss and bad match when the MySQL driver is disconnected.
|
||||
|
|
@ -1 +0,0 @@
|
|||
修复 MySQL 驱动断开连接时出现的数据丢失和匹配错误的问题。
|
||||
|
|
@ -1 +0,0 @@
|
|||
Fix an issue where testing the GCP PubSub could leak memory, and an issue where its JWT token would fail to refresh a second time.
|
||||
|
|
@ -1 +0,0 @@
|
|||
修复了测试GCP PubSub可能泄露内存的问题，以及其JWT令牌第二次刷新失败的问题。
|
||||
|
|
@ -1,3 +0,0 @@
|
|||
Fix some issues that could lead to wrong bridge metrics.
|
||||
Fix and issue that could lead to message loss and wrong metrics with Kafka Producer bridge when Kafka or the connection to it is down.
|
||||
Fix some issues that could lead to the same message being delivered more than once when using batching for bridges and when the batch was retried.
|
||||
|
|
@ -1,3 +0,0 @@
|
|||
修复一些可能导致错误桥接指标的问题。
|
||||
修复当Kafka或其连接中断时，可能导致Kafka Producer桥的消息丢失和错误指标的问题。
|
||||
修复一些问题，这些问题可能导致在为桥接使用批处理时，同一消息被多次传递，以及批处理被重试时。
|
||||
|
|
@ -1 +0,0 @@
|
|||
Remove possibility to set `clientid` for `/publish` and `/publish/bulk` HTTP APIs. This is to reduce the risk for security confusion.
|
||||
|
|
@ -1 +0,0 @@
|
|||
从 HTTP API /publish 和 /publish/bulk 中移除 clientid, 降低安全风险
|
||||
|
|
@ -1 +0,0 @@
|
|||
Fix the problem that the bridge is not available when the Payload template is empty in the MQTT bridge.
|
||||
|
|
@ -1 +0,0 @@
|
|||
修复 MQTT 桥接中 Payload 模板为空时桥接不可用的问题。
|
||||
|
|
@ -1 +0,0 @@
|
|||
When deleting a non-existing bridge the server gave a success response. This has been fixed so that the server instead gives an error response when the user attempts to delete a non-existing bridge.
|
||||
|
|
@ -1 +0,0 @@
|
|||
修复了当通过 API 删除一个不存在的桥接时，服务器会返回操作成功的问题，现在将会返回操作失败的信息。
|
||||
|
|
@ -1,2 +0,0 @@
|
|||
Fix the problem that sending messages to data-bridges failed because of incorrect handling of some data-bridges without `local_topic` field configured.
|
||||
Before this change, if some bridges have configured the `local_topic` field but others have not, a `function_clause` error will occur when forwarding messages to the data-bridges.
|
||||
|
|
@ -1,2 +0,0 @@
|
|||
修复由于某些数据桥接未配置 `local_topic` 字段，导致的所有数据桥接无法发送消息。
|
||||
在此改动之前，如果有些桥接设置了 `local_topic` 字段而有些没有设置，数据桥接转发消息时会出现 `function_clause` 的错误。
|
||||
|
|
@ -1 +0,0 @@
|
|||
Fix handling of HTTP authorization result when a request failure (e.g.: HTTP resource is down) would cause a `function_clause` error.
|
||||
|
|
@ -1 +0,0 @@
|
|||
修正当请求失败（如：HTTP资源关闭）会导致`function_clause`错误时对HTTP授权结果的处理。
|
||||
|
|
@ -1,3 +0,0 @@
|
|||
Set the default value of the `qos` field of the HTTP API `/clients/:clientid/subscribe` to 0.
|
||||
Before this fix, the `qos` field have no default value, which leads to a `function_clause` error
|
||||
when querying this API.
|
||||
|
|
@ -1,2 +0,0 @@
|
|||
将 HTTP 接口 `/clients/:clientid/subscribe` 的 `qos` 字段的默认值设置为 0。
|
||||
在此修复之前，`qos` 字段没有默认值，调用订阅接口的时候将导致 `function_clause` 错误。
|
||||
|
|
@ -1,8 +0,0 @@
|
|||
Remove the default value of Webhook.
|
||||
Before this repair, the default value of the `body` field of Webhook is `${payload}`,
|
||||
but there is no `payload` field in the available fields of other events except message
|
||||
publishing in the rule, so in this case, the webhook will send a string with the
|
||||
message body as "undefined" to the HTTP service.
|
||||
This fix removes the default value of the `body` field. When the `body` field is
|
||||
not configured, Webhook will send all available fields of the current event in
|
||||
the format of JSON object.
|
||||
|
|
@ -1,5 +0,0 @@
|
|||
删除 Webhook 的默认值。
|
||||
在此修复之前，Webhook 的 `body` 字段的默认值为 `${payload}`，但规则中除了消息发布之外的其他事件的可用字段中
|
||||
都没有 `payload` 字段，所以这种情况下 Webhook 将发送消息正文为 "undefined" 的字符串到 HTTP 服务。
|
||||
此修复移除了 `body` 字段的默认值，当未配置 `body` 字段的时候，Webhook 将以 JSON object 的格式发送
|
||||
当前事件的全部可用字段。
|
||||
|
|
@ -1,2 +0,0 @@
|
|||
Fixed the problem of '404 Not Found' when calling the HTTP API '/clients/:clientid/subscribe/bulk'
|
||||
from the plug-ins and data-bridges on handling the 'client.connected' event.
|
||||
|
|
@ -1,2 +0,0 @@
|
|||
修复了监听 `client.connected` 事件的插件和数据桥接在调用 `/clients/:clientid/subscribe/bulk`
|
||||
HTTP 接口时报 `404 Not Found` 的问题。
|
||||
|
|
@ -1 +0,0 @@
|
|||
Fix `/mqtt/auto_subscribe` API's bad swagger schema, and make sure swagger always checks if the schema is correct.
|
||||
|
|
@ -1 +0,0 @@
|
|||
修复 `/mqtt/auto_subscribe` API 错误的 swagger 格式，并且保证 swagger 总是检查格式是否正确。
|
||||
|
|
@ -1 +0,0 @@
|
|||
MQTT bridge config compatibility fix. The config created from before v5.0.12 may encounter a compatibility issue after upgraded to v5.0.13.
|
||||
|
|
@ -1 +0,0 @@
|
|||
修复 v5.0.12 之前的 MQTT 桥接配置在 升级到 v5.0.13 后 HTTP API 查询 桥接配置时的一个兼容性问题。
|
||||
|
|
@ -1 +0,0 @@
|
|||
Prior to this fix, if it always times out when trying to connect a bridge server, it's not possible to change other configs even when the bridge is disabled.
|
||||
|
|
@ -1 +0,0 @@
|
|||
修复已禁用的桥接资源服务器连接超时的情况下不能修改其他配置参数的问题。
|
||||
|
|
@ -1 +0,0 @@
|
|||
Potential leaks of atoms that could lead to a crash if a lot of resources were created have been removed.
|
||||
|
|
@ -1 +0,0 @@
|
|||
如果创建了大量的资源，可能会导致崩溃的潜在的原子泄漏已经被删除。
|
||||
|
|
@ -1 +0,0 @@
|
|||
Make authorization config validation error message more readable.
|
||||
|
|
@ -1 +0,0 @@
|
|||
改进授权配置检查错误日志的可读性。
|
||||
Loading…
Reference in New Issue