After Message Queue for MQTT is upgraded from V2.x.x to V3.x.x, its topics are no longer dependent on Message Queue for Apache RocketMQ. Topics of the two services are independent of each other. This article describes the differences in managing topics in the console between the two versions and provides console screenshots for explicit comparison.

Change description

Message Queue for MQTT V3.x.x implements independent message storage. Therefore, you must manage all topics of Message Queue for MQTT in the Message Queue for MQTT console or by calling API operations.

The interaction of topics between Message Queue for MQTT and Message Queue for Apache RocketMQ is disabled. To exchange data between the two services, you must configure rules. For more information, see Cross-product data exchange.

For more information about changes in using resources, see Changes in using resources. For more information about changes in using API operations, see Changes in using the OpenAPIs.

Note You can check whether your instance version is V2.x.x or V3.x.x based on the value of the Kernel version parameter on the Instances page in the console.

Operation changes in the console

The difference between V2.x.x and V3.x.x is that Message Queue for MQTT V3.x.x implements independent storage and its topics no longer depend on the topics of Message Queue for Apache RocketMQ. Therefore, the topic creation path and the effective scope of the topic creation between the two versions are different. The following figures show the console screenshots of different versions.

  • V2.x.x
    • Creation path

      You can create a topic in the Message Queue for MQTT console or in the Message Queue for Apache RocketMQ console.

      • Message Queue for MQTT console

        The GUI elements that are framed in red in the following figure are displayed only in the Message Queue for MQTT V2.x.x console.

      • Message Queue for Apache RocketMQ consolecreate_topic_change_1
    • Effective scope

      Topics created in the Message Queue for MQTT or Message Queue for Apache RocketMQ console are synchronized in the topic list of the two services.

  • V3.x.x
    • Creation path

      In V3.x.x, topics can be created only in the Message Queue for MQTT console.

    • Effective scope

      Topics that are created in the Message Queue for MQTT console take effect only in Message Queue for MQTT and are not synchronized to Message Queue for Apache RocketMQ. Similarly, topics created in the Message Queue for Apache RocketMQ console are not synchronized to Message Queue for MQTT.

      Note The changes in the effective scope of calling API operations are similar to those of control usage.

References

For more information about topic-related operations in the console, see Manage topics.