JiekerTime opened a new issue #9314:
URL: https://github.com/apache/shardingsphere/issues/9314


   ### Which version of ShardingSphere did you use?
   5.0.0-RC1-SNAPSHOT
   
   ### Which project did you use? ShardingSphere-JDBC or ShardingSphere-Proxy?
   ShardingSphere-JDBC
   
   ### Expected behavior
   Do not configure the algorithm rules of the broadcast table
   
   ### Actual behavior
   Have to configure the algorithm rules of the broadcast table
   
   ### Reason analyze (If you can)
   JDBC lacks special handling of broadcast tables
   
   ### Steps to reproduce the behavior, such as: SQL to execute, sharding rule 
configuration, when exception occur etc.
   If you do not config the algorithm rules of broadcast-table:
   
![image](https://user-images.githubusercontent.com/76552510/106851434-32c73680-66f1-11eb-9928-93f48c7b1a42.png)
   And execute the integration sql statement:
   `
   DROP INDEX t_broadcast_table_for_ddl_index ON t_broadcast_table_for_ddl
   `
   You can't read the correct index list:
   
![image](https://user-images.githubusercontent.com/76552510/106851876-fb0cbe80-66f1-11eb-87b2-8592c911f601.png)
   Unlike proxy, jdbc can only load the index list through 
ndexMetaDataLoader.load:
   
![image](https://user-images.githubusercontent.com/76552510/106852255-b9304800-66f2-11eb-9599-e81f395cbe85.png)
   Therefore, you will have to configure the dataNode!
   
   ### Example codes for reproduce this issue (such as a github link).
   About PR:https://github.com/apache/shardingsphere/pull/9313
   


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