v7.2.4

Update Information

Fixed Issues

• [Worksheet] Permission checks for retrieving row record discussions are inaccurate
• [Worksheet] Operating the signature field on H5 may trigger the mobile swipe-back gesture
• [Statistical chart] Excessive map source data may cause the service to become unavailable
• [Org Admin] When editing user information, mobile numbers starting with 0 lose the leading 0 after being saved
• [Org Admin] Time range filtering in application usage analysis is inaccurate
• [Org Admin] Performance issues occur when retrieving department members
• [Collaboration] Attachment size limits do not take effect in IM chats

Upgrade Instruction

Standalone Mode

• Data Backup

• Upgrade microservices to version 7.2.4. Refer to this

• After the image upgrade is completed, execute the script in the microservice application container. The steps are as follows:

  1. Entering the container

     docker exec -it $(docker ps | grep -E 'mingdaoyun-community|mingdaoyun-hap' | awk '{print $1}') bash

  2. Execute the following command(Added indexes to optimize query performance)

     If you are using a non-built-in MySQL database, go to Database Change SQL to obtain the change SQL appropriate for the current upgrade version and database type, then run it in that database.

     If the username and password have been customized, please modify the corresponding parameter values

     mysql -h sc -P 3306 -uroot -p123456 --default-character-set=utf8 -N < /init/mysql/7.2.4/DDL.sql

Cluster Mode

• Backup data storage related servers.

• Upgrade microservices to version 7.2.4. Refer to this

• Enter the config Pod of the control node and execute the following commands, as shown below:

  1. Enter config Pod (note to change the default to the actual namespace)

     kubectl exec -it $(kubectl get pod -n default | grep config | awk '{print $1}') bash -n default

  2. Execute the following script(Added indexes to optimize query performance)

     If you are using a non-MySQL database, go to Database Change SQL to obtain the change SQL appropriate for the current upgrade version and database type, then run it in that database.

     mysql -h $ENV_MYSQL_HOST -P $ENV_MYSQL_PORT -u$ENV_MYSQL_USERNAME -p$ENV_MYSQL_PASSWORD --default-character-set=utf8 -N < /init/mysql/7.2.4/DDL.sql