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 \ http://localhost:8888/shardingscaling/job/start \ -H 'content-type: application/json' \ -d '{ "ruleConfiguration": { "sourceDatasource": "ds_0: !!YamlDataSourceConfiguration\n dataSourceClassName: com.zaxxer.hikari.HikariDataSource\n properties:\n jdbcUrl: jdbc:mysql://127.0.0.1:3306/test?serverTimezone=UTC&useSSL=false\n username: root\n password: '\''123456'\''\n connectionTimeout: 30000\n idleTimeout: 60000\n maxLifetime: 1800000\n maxPoolSize: 50\n minPoolSize: 1\n maintenanceIntervalMilliseconds: 30000\n readOnly: false\n", "sourceRule": "tables:\n t_order:\n actualDataNodes: ds_0.t_order\n tableStrategy:\n none", "destinationDataSources": { "name": "dt_0", "password": "123456", "url": "jdbc:mysql://127.0.0.1:3306/test2?serverTimezone=UTC&useSSL=false", "username": "root" } }, "jobConfiguration": { "concurrency": 3 } }' 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/
