azexcy opened a new issue, #28141: URL: https://github.com/apache/shardingsphere/issues/28141
## Bug Report Related: #28063 There still have problem when create table with unique keys. **1**, It's get unique keys, but after `SchemaMetaDataReviseEngine#revise(org.apache.shardingsphere.infra.database.core.metadata.data.model.SchemaMetaData)` <img width="1122" alt="image" src="https://github.com/apache/shardingsphere/assets/101622833/362d6def-d637-45e5-9101-b12e08f0c928";> The unique keys lost. **2**, unique key does't include unique key column names <img width="1100" alt="image" src="https://github.com/apache/shardingsphere/assets/101622833/c3735d00-cf01-41ce-b027-92a6ff900401";> Maybe they're related. ### Which version of ShardingSphere did you use? master ### Which project did you use? ShardingSphere-JDBC or ShardingSphere-Proxy? ShardingSphere-Proxy ### Expected behavior Unique key load success and have columns ### Actual behavior Not have columns and can't read from metadata. ### Reason analyze (If you can) ### Steps to reproduce the behavior, such as: SQL to execute, sharding rule configuration, when exception occur etc. 1. create table ``` CREATE TABLE t_user (id varchar(20) NOT NULL, username varchar(50), password varchar(50), email varchar(50)) ``` 2. create index ``` CREATE UNIQUE INDEX uk_user_id ON t_user(id); ``` 3. execute `refresh table metadata;` it's will trigger metadata load ``` refresh table metadata; ``` ### 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
