Table meta data is not persisted as expected

[RaigorJiang]

Question

Which version of ShardingSphere did you use?

5.5.2-SNAPSHOT f84f01a

Which project did you use? ShardingSphere-JDBC or ShardingSphere-Proxy?

ShardingSphere-Proxy

Expected behavior

When there are tables in the metadata in memory, the schema/tables in Zookeeper should also have table nodes.

Actual behavior

[Y-sir]

I also found this problem. The problem is that the tables in the SingleRuleConfiguration object created in the getMissedDefaultRuleBuilderMap method in DatabaseRulesBuilder are empty and have no data. Then, in the loadSpecifiedDataNode in the loadSpecifiedDataNodes method in SingleTableDataNodeLoader, it ends as indicated by the arrow in Figure 1. I tried to comment out if (!singleNode.isEmpty()) { in loadSpecifiedDataNodes in Figure 2 and replace the original singleNode object with entry.getValue() and put it in.

Figure 1

Figure 2

[menghaoranss]

fixed by #34236

[Y-sir]

@RaigorJiang @menghaoranss Hello, I found that the table metadata does not exist when the encryption rules are created, but it does not exist when the sharding proxy is started. I remember that the previous versions would load the table metadata when they were first started. Could it be that the metadata loading mechanism of the new version has changed, and the table metadata will only be loaded when new encryption rules are added, and will not be loaded when it is started?