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

Wed, 29 Apr 2020 17:58:20 -0700 

Sorry, I don't know why the blanks  turn into  .




------------------ Original ------------------
From:&nbsp;"KimmKing"<[email protected]&gt;;
Date:&nbsp;Wed, Apr 29, 2020 07:24 PM
To:&nbsp;"dev"<[email protected]&gt;;"birdyanggr"<[email protected]&gt;;

Subject:&nbsp;Re:[SHARDING-SCALING]Optimization about job start API



a text format mail is better.





At 2020-04-29 13:35:13, "sushixiang" <[email protected]&gt; wrote:
&gt;Hi everyone,&amp;nbsp;
&gt;As we know, sharding-scaling can be used for migrating data from single 
datasource to ShardingSphere when first using ShardingSphere,&amp;nbsp;and the 
start API is showed below:
&gt;
&gt;
&gt;curl -X POST \
&gt;&amp;nbsp; http://localhost:8888/shardingscaling/job/start \
&gt;&amp;nbsp; -H 'content-type: application/json' \
&gt;&amp;nbsp; -d '{
&gt;&amp;nbsp; &amp;nbsp;"ruleConfiguration": {
&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; "sourceDatasource": "ds_0: 
!!YamlDataSourceConfiguration\n&amp;nbsp; dataSourceClassName: 
com.zaxxer.hikari.HikariDataSource\n&amp;nbsp; properties:\n&amp;nbsp; 
&amp;nbsp; jdbcUrl: 
jdbc:mysql://127.0.0.1:3306/test?serverTimezone=UTC&amp;amp;useSSL=false\n&amp;nbsp;
 &amp;nbsp; username: root\n&amp;nbsp; &amp;nbsp; password: 
'\''123456'\''\n&amp;nbsp; &amp;nbsp; connectionTimeout: 30000\n&amp;nbsp; 
&amp;nbsp; idleTimeout: 60000\n&amp;nbsp; &amp;nbsp; maxLifetime: 
1800000\n&amp;nbsp; &amp;nbsp; maxPoolSize: 50\n&amp;nbsp; &amp;nbsp; 
minPoolSize: 1\n&amp;nbsp; &amp;nbsp; maintenanceIntervalMilliseconds: 
30000\n&amp;nbsp; &amp;nbsp; readOnly: false\n",
&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; "sourceRule": "tables:\n&amp;nbsp; 
t_order:\n&amp;nbsp; &amp;nbsp; actualDataNodes: ds_0.t_order\n&amp;nbsp; 
&amp;nbsp; tableStrategy:\n&amp;nbsp; &amp;nbsp; &amp;nbsp; none",
&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; "destinationDataSources": {
&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;"name": "dt_0",
&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;"password": "123456",
&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;"url": 
"jdbc:mysql://127.0.0.1:3306/test2?serverTimezone=UTC&amp;amp;useSSL=false",
&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;"username": "root"
&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; }
&gt;&amp;nbsp; &amp;nbsp;},
&gt;&amp;nbsp; &amp;nbsp;"jobConfiguration": {
&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; "concurrency": 3
&gt;&amp;nbsp; &amp;nbsp;}
&gt;}'
&gt;
&gt;
&gt;
&gt;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.
&gt;
&gt;
&gt;So, I think a simpler configuration may be needed, not only the first data 
migrate scenario, does anyone has some suggestions about it?
&gt;
&gt;
&gt;All data migrate scenarios can refer the 
link:&amp;nbsp;https://shardingsphere.apache.org/document/current/en/features/sharding-scaling/core-features/

Reply via email to