strongduanmu commented on issue #10996: URL: https://github.com/apache/shardingsphere/issues/10996#issuecomment-888858430
In order to solve the single table routing in the multi-data source aggregation scenario, the order of the rule needs to be adjusted. The latest order is as follows. <div class="okr-block-clipboard" data-okr="%7B%22okrDelta%22%3A%5B%7B%22lineType%22%3A%22unsupport%22%2C%22lineOptions%22%3A%7B%7D%2C%22lineContent%22%3A%5B%5D%7D%5D%2C%22businessKey%22%3A%22lark-doc%22%7D"></div><div data-zone-id="0" data-line-index="0" style="white-space: pre;"> Type | Order | Use -- | -- | -- ShardingRule | ShardingOrder——0 | ShardingTableMetaDataBuilder ShardingSQLRewriteContextDecorator ShardingResultMergerEngine ShardingSQLRouter SingleTableRule | SingleTableOrder——10 | SingleTableSQLRouter EncryptRule | EncryptOrder——20 | EncryptTableMetaDataBuilder EncryptSQLRewriteContextDecorator EncryptResultDecoratorEngine ReadwriteSplittingRule | ReadwriteSplittingOrder——30 | ReadwriteSplittingSQLRouter DatabaseDiscoveryRule | DatabaseDiscoveryOrder——40 | DatabaseDiscoverySQLRouter ShadowRule | ShadowOrder——50 | ShadowSQLRewriteContextDecorator ShadowSQLRouter </div> As shown in the figure below, the kernel execution will be executed in ascending order of order.  When the rule is initialized, the data source aggregation rule needs to be loaded in reverse order to ensure that it can be routed from the logical data source to the real data source during routing.  -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
