duanzonglong opened a new issue #6759:
URL: https://github.com/apache/shardingsphere/issues/6759


   ## Bug Report
   
   **For English only**, other languages will not accept.
   
   Before report a bug, make sure you have:
   
   - Searched open and closed [GitHub 
issues](https://github.com/apache/shardingsphere/issues).
   - Read documentation: [ShardingSphere 
Doc](https://shardingsphere.apache.org/document/current/en/overview).
   
   Please pay attention on issues you submitted, because we maybe need more 
details. 
   If no response anymore and we cannot reproduce it on current information, we 
will **close it**.
   
   Please answer these questions before submitting your issue. Thanks!
   
   ### Which version of ShardingSphere did you use?
   4.1.1
   
   ### Which project did you use? ShardingSphere-JDBC or ShardingSphere-Proxy?
   ShardingSphere-Proxy
   
   ### Expected behavior
   config-wms.yaml:
   shardingRule:
     defaultDatabaseStrategy:
       standard:
         shardingColumn: tenant_id
         preciseAlgorithmClassName: 
com.hrsoft.sharding.strategy.core.DatabaseStrategy
     tables:
       databasechangeloglock:
         actualDataNodes: wms_base.databasechangeloglock
         databaseStrategy:
           none:
         tableStrategy:
           none:
       databasechangelog:
         actualDataNodes: wms_base.databasechangelog
         databaseStrategy:
           none:
         tableStrategy:
           none:
   
   
   
   ### Actual behavior
   Table 'wms_sd1.databasechangelog' doesn't exist
   some times its ok,so i think the "DatabaseStrategy" got wrong
   
   
   ### Steps to reproduce the behavior, such as: SQL to execute, sharding rule 
configuration, when exception occur etc.
   springliquibase:
   SHOW FULL COLUMNS FROM `databasechangelog` FROM `sharding_wms` LIKE '%'
   
   ### Example codes for reproduce this issue (such as a github link).
   


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


Reply via email to