Re:[SHARDING-SCALING]Optimization about job start API

[KimmKing]

Hi, ssxlulu,
    Glad to know you want optimize scaling rule with original datasources from 
certain sharding tables to all tables.
    Can you show a detailed solution? Expecting further more improvement of you.

At 2020-04-30 08:56:31, "sushixiang" <shixian...@qq.com> wrote:
>Hi everyone, 
>As we know, sharding-scaling can be used for migrating data from single 
>datasource to ShardingSphere when first using ShardingSphere, and the start 
>API is showed below:
>
>
>
>
>curl -X POST \
>&nbsp; http://localhost:8888/shardingscaling/job/start \
>&nbsp; -H 'content-type: application/json' \
>&nbsp; -d '{
>&nbsp; &nbsp;"ruleConfiguration": {
>&nbsp; &nbsp; &nbsp; "sourceDatasource": "ds_0: 
>!!YamlDataSourceConfiguration\n&nbsp; dataSourceClassName: 
>com.zaxxer.hikari.HikariDataSource\n&nbsp; properties:\n&nbsp; &nbsp; jdbcUrl: 
>jdbc:mysql://127.0.0.1:3306/test?serverTimezone=UTC&amp;amp;useSSL=false\n&nbsp;
> &nbsp; username: root\n&nbsp; &nbsp; password: '\''123456'\''\n&nbsp; &nbsp; 
>connectionTimeout: 30000\n&nbsp; &nbsp; idleTimeout: 60000\n&nbsp; &nbsp; 
>maxLifetime: 1800000\n&nbsp; &nbsp; maxPoolSize: 50\n&nbsp; &nbsp; 
>minPoolSize: 1\n&nbsp; &nbsp; maintenanceIntervalMilliseconds: 30000\n&nbsp; 
>&nbsp; readOnly: false\n",
>&nbsp; &nbsp; &nbsp; "sourceRule": "tables:\n&nbsp; t_order:\n&nbsp; &nbsp; 
>actualDataNodes: ds_0.t_order\n&nbsp; &nbsp; tableStrategy:\n&nbsp; &nbsp; 
>&nbsp; none",
>&nbsp; &nbsp; &nbsp; "destinationDataSources": {
>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"name": "dt_0",
>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"password": "123456",
>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"url": 
>"jdbc:mysql://127.0.0.1:3306/test2?serverTimezone=UTC&amp;amp;useSSL=false",
>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"username": "root"
>&nbsp; &nbsp; &nbsp; }
>&nbsp; &nbsp;},
>&nbsp; &nbsp;"jobConfiguration": {
>&nbsp; &nbsp; &nbsp; "concurrency": 3
>&nbsp; &nbsp;}
>}'
>
>
>
>
>
>But I think the configuration may be much complex for the fisrt use, if we 
>need migrate all tables from the source database, we should config all tables 
>in the 'sourceRule' item, and for first use, we may not have the concept of 
>table rules.
>
>
>
>
>So, I think a simpler configuration may be needed, not only the first data 
>migrate scenario, does anyone has some suggestions about it?
>
>
>
>
>All data migrate scenarios can refer the link: 
>https://shardingsphere.apache.org/document/current/en/features/sharding-scaling/core-features/