After a Message Queue for MQTT instance is upgrade from V2.x.x to V3.x.x, it implements independent storage, that means topic resources are no longer dependent on Message Queue for Apache RocketMQ. Therefore, topics of the two services are completely independent of each other. This topic describes the differences in topic resource console operations between the two versions and provides corresponding console screenshots for explicit comparison.

Change description

Message Queue for MQTT of V3.x.x implements independent message storage. Therefore, all topic resources of a Message Queue for MQTT instance must be managed in the Message Queue for MQTT console or by invoking its OpenAPI.

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

For more information about change description, see Changes in using resources. For more information about OpenAPI changes, see Changes in using the OpenAPIs.

Note You can determine whether your instance version is V2.x.x or V3.x.x based on the Kernel version field on the Instance Information tab of the Instances page in the console.

Console usage changes

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

  • V2.x.x
  • V3.x.x
    • Creation path
      In V3.x.x, topics can be created only in the Message Queue for MQTT console. You can see the contents highlighted in the red boxes only in V3.x.x.create_topic_change_2
    • Effective range

      Topics 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 range of invoking the OpenAPI are similar to those of control usage.

References

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