[GitHub] [shardingsphere] sandynz commented on a diff in pull request #22586: Add refer link at migration document

[GitBox <gi...@apache.org>]

sandynz commented on code in PR #22586:
URL: https://github.com/apache/shardingsphere/pull/22586#discussion_r1037873076


##########
docs/document/content/user-manual/shardingsphere-proxy/migration/usage.cn.md:
##########
@@ -486,34 +490,35 @@ max_connections = 600
 ```
 host replication repl_acct 0.0.0.0/0 md5
 ```
+
 3. 赋予数据库和表的访问权限
 
-如果使用非超级管理员账号进行迁移，要求该账号在迁移时用到的数据库上，具备 CREATE，和 CONNECT 的权限。
+如果使用非超级管理员账号进行迁移，要求该账号在迁移时用到的数据库上，具备 CREATE 和 CONNECT 的权限。
 
 示例：
 
 ```sql
-GRANT CREATE, CONNECT ON DATABASE migration_ds_0 TO normal_user;
+GRANT CREATE, CONNECT ON DATABASE migration_ds_0 TO migration_user;
 ```
 
 还需要账号对迁移的表和 schema 具备访问权限，以 test schema 下的 t_order 表为例。
 
 ```sql
 \c migration_ds_0
 
-GRANT USAGE ON SCHEMA test TO GROUP normal_user;
-GRANT SELECT ON TABLE test.t_order TO normal_user;
+GRANT USAGE ON SCHEMA test TO GROUP migration_user;
+GRANT SELECT ON TABLE test.t_order TO migration_user;
 ```
 
 openGauss 有 OWNER 的概念，如果是数据库，SCHEMA，表的 OWNER，则可以省略对应的授权步骤。
 
-openGauss 因为安全原因，不允许普通客户在 public 模式下操作。所以如果迁移的表在 public 模式下，需要额外授权。
+openGauss 不允许普通客户在 public schema 下操作。所以如果迁移的表在 public schema 下，需要额外授权。
 
 ```sql
-GRANT ALL PRIVILEGES TO normal_user;
+GRANT ALL PRIVILEGES TO migration_user;
 ```
 
-详情请参见 [Configuring Client Access Authentication](https://opengauss.org/en/docs/2.0.1/docs/Developerguide/configuring-client-access-authentication.html) 和 [Example: Logic Replication Code](https://opengauss.org/en/docs/2.0.1/docs/Developerguide/example-logic-replication-code.html)。

Review Comment:
   It could be put to section 2



-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscribe@shardingsphere.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org