MySQL Bugs: #103157: Inconsistent terminology change in error messages

Bug #103157	Inconsistent terminology change in error messages
Submitted:	30 Mar 2021 22:01	Modified:	31 Mar 2021 6:31
Reporter:	Przemyslaw Malkowski	Email Updates:
Status:	Verified	Impact on me:	None
Category:	MySQL Server: Replication	Severity:	S3 (Non-critical)
Version:	8.0.23	OS:	Any
Assigned to:		CPU Architecture:	Any

Description:
So terminology has changed via https://dev.mysql.com/worklog/task/?id=14189, yet I can see at least one inconsistency in how it was implemented. An error message still suggests using the old command:

mysql > CHANGE REPLICATION SOURCE TO SOURCE_DELAY=1 FOR CHANNEL "node2";
ERROR 3085 (HY000): This operation cannot be performed with a running slave sql thread; run STOP SLAVE SQL_THREAD FOR CHANNEL 'node2' first.

How to repeat:
On a working replica node, try to change parameter that requires stopping SQL thread.

Tested with: 

mysql > select @@version,@@version_comment;
+-----------+------------------------------+
| @@version | @@version_comment            |
+-----------+------------------------------+
| 8.0.23    | MySQL Community Server - GPL |
+-----------+------------------------------+
1 row in set (0.00 sec)

Suggested fix:
Make sure error messages do not use deprecated terminology.

Hello Przemyslaw,

Thank you for the report.

regards,
Umesh