This topic describes the new features, feature optimizations, and important bug fixes in each release of Message Queue for MQTT. This topic also provides references to help you understand the updates of Message Queue for MQTT.
|Cloud SDK V1.0.4.Final (server-sdk-1.0.4.Final)||
|Cloud SDK||The cloud SDK is provided in Message Queue for MQTT. The cloud SDK allows backend applications in the cloud to directly connect to Message Queue for MQTT without the need to use other Alibaba Cloud services. The cloud SDK supports the
clustering consumption of messages. Messages can be consumed by different backend
applications on which the cloud SDK is installed.
To use the cloud SDK, submit a ticket to enable this feature.
|API operations for querying traces||The traces and messages of a device that corresponds to a Message Queue for MQTT client and the traces of a message can be queried.||New|
|Subscription relationship cleanup||Subscription relationships can be cleared for a specified topic in the Message Queue for MQTT console. If a consumer keeps offline for a period of time that exceeds the specified threshold, Message Queue for MQTT deletes the subscription relationship between the consumer and the topic.||New||Clear subscriptions for a topic|
|New version of the console||The Message Queue for MQTT console is updated to improve user experience.||Optimized|
|Change of the billing method from subscription to pay-as-you-go||The billing method of a Message Queue for MQTT instance can be changed from subscription to pay-as-you-go.||New||Change the billing method of an instance from subscription to pay-as-you-go|
|API operation for sending messages from a backend application||The API operation for sending messages from a backend application is added.||New||SendMessage|
|API operation for Message Queue for MQTT client status query||The status of one or more Message Queue for MQTT clients can be queried at a time.||New|
|Kernel version update||The versions before and after the kernel version of an instance is updated are differentiated. The versions before the update are unified to V2.x.x, and the versions after the update are unified to V3.x.x.||New||Changes in instance management|
|Cross-service data exchange rules||
|Independent storage||In V3.x.x and later, Message Queue for MQTT no longer uses Message Queue for Apache RocketMQ to store messages, and topics of the two services are no longer interconnected by default. To exchange data between the two services, you must create and use data exchange rules. Message Queue for MQTT V3.x.x provides separate API operations to manage topics.||New|
|API||Tokens can be obtained by calling API operations.||New||List of operations by function|