fantacy2001 edited a comment on issue #4861: two tables left join with different routing rules are not supported URL: https://github.com/apache/incubator-shardingsphere/issues/4861#issuecomment-604187682 > What is your sharding rule configuration? sharding rule: <sharding:table-rule logic-table="a" actual-data-nodes="ds_ms$->{0..1}.a" database-strategy-ref="databaseStrategy" /> <sharding:table-rule logic-table="b" actual-data-nodes="ds_ms0.b_000,ds_ms$->{0..1}.b_00$->{1..3}" database-strategy-ref="databaseStrategy" table-strategy-ref="tableStrategy" /> <sharding:standard-strategy id="databaseStrategy" sharding-column="col" precise-algorithm-ref="commonDBShardingAlgorithm"/> <sharding:standard-strategy id="tableStrategy" sharding-column="col" precise-algorithm-ref="tableShardingAlgorithm"/> in the db and table ShardingAlgorithm, i mapping the dbs and tables by columns 'col', like: Map dbMap = new HashMap(); static{ dbMap.put("123","db_01"); dbMap.put("125","db_02") } Map tableMap = new HashMap(); static{ tableMap.put("123","table_001"); tableMap.put("125","table_002") } i mean on the join condition, Whether the sharding key after "on" should be transitive？ I didn't find it in the source code.
---------------------------------------------------------------- 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. For queries about this service, please contact Infrastructure at: [email protected] With regards, Apache Git Services
