[GitHub] [shardingsphere] azexcy opened a new issue, #17993: ALTER SHARDING TABLE RULE , datasource changed effect early, before apply scaling

[GitBox]

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

   ## Bug Report
   
   when execute `ALTER SHARDING TABLE RULE ` before `apply scaling `
   ```
   ALTER SHARDING TABLE RULE t_order(
           RESOURCES(ds_2, ds_3, ds_4),
           SHARDING_COLUMN=order_id,
           TYPE(NAME=hash_mod,PROPERTIES("sharding-count"=6)),
           KEY_GENERATE_STRATEGY(COLUMN=order_id,TYPE(NAME=snowflake))
           )
   ```
   then the `PREVIEW SELECT COUNT(1) FROM t_order` result is not correct.
   
   <img width="1028" alt="image" 
src="https://user-images.githubusercontent.com/101622833/170626373-641de892-0248-4be5-86a8-61103a83c4c5.png";>
   
   
   <img width="1105" alt="image" 
src="https://user-images.githubusercontent.com/101622833/170625816-8e68ffce-2a02-4be0-9284-0f587236d686.png";>
   
   the 
org.apache.shardingsphere.integration.data.pipeline.cases.base.BaseITCase code 
below
   
   <img width="1162" alt="image" 
src="https://user-images.githubusercontent.com/101622833/170626095-a4a4eadd-de72-4336-8984-5eb64e4ee107.png";>
   
   relation action link 
https://github.com/apache/shardingsphere/runs/6619785021?check_suite_focus=true#step:6:2791
   
   ### Which version of ShardingSphere did you use?
   
   master 10bebf6517a337a9113d5682cae09d46f189ca8a
   
   ### Which project did you use? ShardingSphere-JDBC or ShardingSphere-Proxy?
   
   ShardingSphere-Proxy
   
   ### Expected behavior
   
   sharding rule effect after apply scaling
   
   ### Actual behavior
   
   sharding rule effect before apply scaling, after ALTER SHARDING TABLE RULE
   
   ### Reason analyze (If you can)
   
   maybe the event cause, the info of this action below（immediately after 
`ALTER SHARDING TABLE RULE`)
   ```
   [INFO ] 2022-05-27 03:27:27.283 [docker-java-stream-136750828] 
:Scaling-Proxy - [INFO ] 2022-05-27 03:27:27.264 [Curator-SafeNotifyService-0] 
o.a.s.m.m.c.c.r.c.s.ScalingRegistrySubscriber - schemaChanged, 
databaseName=sharding_db, schemaName=public, changedTableName=null, 
deletedTable=t_order
   ```
   
   ### Steps to reproduce the behavior, such as: SQL to execute, sharding rule 
configuration, when exception occur etc.
   
   the problem not reproduce everytime, but the action will reproduce it.
   
   ### 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.

To unsubscribe, e-mail: 
notifications-unsubscr...@shardingsphere.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org