jlovej opened a new issue, #21874:
URL: https://github.com/apache/shardingsphere/issues/21874

   Service Description: The sharding Key is not a database field, but needs to 
be divided according to the business logic, so it needs to use a custom forced 
sharding algorithm
   
   Environment configuration: springboot+dubbo+ss5.1.2+seata
   
   Problem description: according to the official documentation, implementation 
HintShardingAlgorithm interfaces, and configuration of the services, at the 
same time according to the official documentation, where calls using 
HintManager. SetDatabaseShardingValue to set the shard
   
   Related configuration:
   
   
![a7cb313955f540f4906a7ca0acad1172](https://user-images.githubusercontent.com/8819998/199049707-b6f0ad28-d2a4-4baa-9e97-cef7ef95e098.png)
   
   services config
   
![c1182f854aac47ebbc461e443ebae962](https://user-images.githubusercontent.com/8819998/199049968-06483f77-df1a-4f3e-83bd-f7619887fb50.png)
   
   Relevant code:
   
   Customize the sharding algorithm
   
![6a3cd19289e64eb69f9425b8f2d0c5f5](https://user-images.githubusercontent.com/8819998/199050368-8131482a-0bec-4f97-bca5-435141e638d6.png)
   
   
![6046ebf3336b4c7cb61993161e494294](https://user-images.githubusercontent.com/8819998/199050708-e420db79-95b3-4672-9ba3-1b36e719192b.png)
   
   Logs are executed after the function is enabled:
   
   
![82e873f8e9e341da8cfe47c9855243ea](https://user-images.githubusercontent.com/8819998/199051208-e22ddaac-1daa-497a-bdb8-2b2acae85ed2.png)
   
   In theory, ds-hlm data source should be used,But we're actually going to 
ds-0:
   
   ![Uploading 8e5e9f638856492d9e0b4693242252df.png…]()
   
   May I ask which configurations are wrong or missing? Please check and look 
forward to your reply
   
   


-- 
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]

Reply via email to