sandynz commented on issue #15532:
URL:
https://github.com/apache/shardingsphere/issues/15532#issuecomment-1082590311
Since there's no exact reproduct steps.
I tried on master branch, commit 6fd57154632ea0f108f9e991b1721ad1c9660aed.
On existing schema `test1`, execute SQLs:
```
mysql> CREATE SHARDING BROADCAST TABLE RULES (t_broadcast_table);
Query OK, 0 rows affected (0.42 sec)
mysql> CREATE TABLE t_broadcast_table (id INT NOT NULL, status VARCHAR(45)
NULL, PRIMARY KEY (id));
Query OK, 0 rows affected (0.39 sec)
mysql> 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,PROPERTIES("worker-id"=123)))
-> ), t_order_item(
-> 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,PROPERTIES("worker-id"=123)))
-> );
Query OK, 0 rows affected (0.26 sec)
```
`t_broadcast_table` always exist in registry center after created.
We'll check it again when developing broadcast table support of scaling job.
--
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]
