You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@shardingsphere.apache.org by GitBox <gi...@apache.org> on 2021/02/01 06:52:22 UTC

[GitHub] [shardingsphere] AI1186780944 commented on issue #9228: How can shardingsphere use read-write separation and data desensitization at the same time?

AI1186780944 commented on issue #9228:
URL: https://github.com/apache/shardingsphere/issues/9228#issuecomment-770617637


   Hi @tristaZero 
   Thanks for your feedback. The configuration doesn't work.Your code implementation logic doesn't support this kind of collocation.The reason is that there are two data sources:"encrypydatasource" and "masterslavedatasource".They are created by two DataSourceFactory.Because there are two DataSourceFactory, two transaction managers are generated. This will make the spring container not know which TransactionManager to register, resulting in an error.Moreover, EncrypyDatasourceFactoryand MasterSlavedDatasourceFactory do not provide an interface that allows users to specify transaction managers freely.
   Your version of 5.0.0-alpha is supported.Because the data source type accepted by this data source factory is map type.I can create my various configuration rules and data sources in the same factory. Only one transaction manager is generated.


----------------------------------------------------------------
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:
users@infra.apache.org