After ApsaraMQ for MQTT is upgraded from V2.x.x to V3.x.x, ApsaraMQ for MQTT topics and ApsaraMQ for RocketMQ topics are independent of each other. This topic describes the differences in topic management in the console between V2.x.x and V3.x.x and provides console screenshots to show the differences.
Change description
ApsaraMQ for MQTT V3.x.x implements independent data storage. You must manage ApsaraMQ for MQTT topics in the ApsaraMQ for MQTT console or by calling API operations.
ApsaraMQ for MQTT topics and ApsaraMQ for RocketMQ topics are no longer interconnected. To exchange data between the two services, you must create data exchange rules. For more information, see Data exchange across cloud services.
For information about the changes in resource use, see Changes in resource use. For information about changes in API operations, see Changes in API operations.
Operation changes in the console
Compared with ApsaraMQ for MQTT V2.x.x, ApsaraMQ for MQTT V3.x.x implements independent data storage. Topics in ApsaraMQ for MQTT V3.x.x are independent of ApsaraMQ for RocketMQ topics. The path for creating a topic and the effective scope of a created topic vary based on the version. The following section describes the creation processes. Screenshots are provided to help you better understand the process.
V2.x.x
Creation path
You can create a topic in the ApsaraMQ for MQTT console or the ApsaraMQ for RocketMQ console.
ApsaraMQ for MQTT console
The GUI elements in the red box in the following figure are displayed only in the ApsaraMQ for MQTT V2.x.x console.
ApsaraMQ for RocketMQ console

Effective scope
Topics created in the ApsaraMQ for MQTT or ApsaraMQ for RocketMQ console are synchronized between the topic lists of the two services.
V3.x.x
Creation path
In ApsaraMQ for MQTT V3.x.x, you can create topics only in the ApsaraMQ for MQTT console.
Effective scope
Topics created in the ApsaraMQ for MQTT console take effect only in ApsaraMQ for MQTT and are not synchronized to ApsaraMQ for RocketMQ. Similarly, topics created in the ApsaraMQ for RocketMQ console are not synchronized to ApsaraMQ for MQTT.
NoteThe changes in the effective scope of calling API operations are similar to the changes in the effective scope of the console operations.
References
For information about how to manage topics in the ApsaraMQ for MQTT console, see Manage topics.