Project: EMQ Technologies (App Definition and Development / Streaming & Messaging)
File: e5.0.2.en.md

Release installation packages for Rocky Linux 9 (compatible with Red Hat Enterprise Linux 9) and macOS 12 for Intel platform. Add `extraVolumeMounts` to EMQX Helm Chart, you can mount user's own files to EMQX instance, such as ACL rule files mentioned in . When connecting with the flag `clean_start=false`, EMQX will filter out messages that published by clients banned by the blacklist feature in the session. Previously, messages sent by clients banned by the blacklist feature could still be delivered to subscribers in this case. Add MQTT ingress to helm charts and remove obsolete mgmt references. Implement Kafka Consumer Bridge, which supports consuming messages from Kafka and publishing them to MQTT topics. Improve error logging related to health checks for InfluxDB connections. Improve the performance of `/bridges` API. Earlier, when the number of nodes in the cluster was large or the node was busy, the API may had a request timeout. Obfuscate request body in error log when using HTTP service for client authentication for security reasons. Metrics are now only exposed via the `/bridges/:id/metrics` endpoint, and no longer returned in other API operations. Improve startup failure logs in daemon mode. Fix return type structure for error case in API schema for `/gateways/:name/clients`. Ensure Monitor API `/monitor(_current)/nodes/:node` returns `404` instead of `400` if node does not exist. Allow setting node name via environment variable `EMQXNODE_NAME` in Docker. Ensure Bridge API returns `404` status code consistently for resources that don't exist. The configuration parameter `mqtt.maxawaitingrel` was not functional and has now been corrected. Fix `/bridges` API status code. Return `400` instead of `403` in case of removing a data bridge that is dependent on an active rule. Return `400` instead of `403` in case of calling operations (start|stop|restart) when Data-Bridging is not enabled. Improve error messages for `/briges_probe` and `[/node/:node]/bridges/:id/:operation` API calls to make them more readable. And set HTTP status code to `400` instead of `500`. Check if type in `PUT /authorization/sources/:type` matches `type` given in the request body. Fix wrong description about

Consistently return `404` for all requests on non-existent source in `/authorization/sources/:source[/*]`. Fix an issue where the MongoDB connector crashed when MongoDB authorization was configured. Fix channel crash for slow clients with enhanced authentication. Previously, when the client was using enhanced authentication, but the Auth message was sent slowly or the Auth message was lost, the client process would crash. For operations on Bridges API if `bridge-id` is unknown we now return `404` instead of `400`. Fix an error occurring when a joining node doesn't have plugins that are installed on other nodes in the cluster. After this fix, the joining node will copy all the necessary plugins from other nodes. Fix problems related to manual joining of EMQX replicant nodes to the cluster. Fix crash when `statsd.server` is set to an empty string. The default heartbeat period for MongoDB has been increased to reduce the risk of too excessive logging to the MongoDB log file. Fix garbled config display in dashboard when the value is originally from environment variables. Fix some error logs generated by `systemctl stop emqx` command. Prior to the fix, the command was not stopping `jq` and `os_mon` applications properly. Fix an issue where emqx cli failed to set the Erlang cookie when the emqx directory was read-only. Change the default `resumeinterval` for bridges and connectors to be the minimum of `healthcheckinterval` and `requesttimeout / 3` to resolve issue of request timeout. Fix default rate limit configuration not being applied correctly when creating a new listener. Ensure we return `404` status code for unknown node names in `/nodes/:node[/metrics|/stats]` API. Fix an issue where rule dependencies were not prompted when deleting an ingress-type bridge in use. Ensure that when the core or replicant node starting, the `cluster-override.conf` file is only copied from the core node. Don't increase actions.failed.unknown rule metrics counter upon receiving unrecoverable data bridge errors. Fix an issue where when the MySQL connector was in batch mode, clients would keep querying the server with unnecessary `PREPARE` statements on each batch, possibly causing server resource exhaustion.