terrymanu commented on issue #37997:
URL:
https://github.com/apache/shardingsphere/issues/37997#issuecomment-3885146266
Thanks for the report.
After checking the current docs and implementation, this is a
configuration usage issue.
For `!SHARDING` rules, the required format is:
- `logicTable` must be a pure table name (for example: `t_order`), not
`schema.table`.
- `actualDataNodes` must be `dataSourceName.actualTableName` (for example:
`ds_${0..1}.t_order_${0..1}`).
Example:
```yaml
rules:
- !SHARDING
tables:
t_order:
actualDataNodes: ds_${0..1}.t_order_${0..1}
Your expected configuration mode (schema.table in sharding rule, such as
base.t_order / ds.base.t_order) is not supported at this time.
Please note: PostgreSQL 3-tier examples like ds_0.public.t_config are
documented for !SINGLE rule, not for !SHARDING.
References:
-
https://shardingsphere.apache.org/document/current/en/user-manual/shardingsphere-jdbc/yaml-config/rules/sharding/
-
https://shardingsphere.apache.org/document/current/en/user-manual/shardingsphere-jdbc/yaml-config/rules/single/
-
https://shardingsphere.apache.org/document/current/en/user-manual/shardingsphere-jdbc/java-api/rules/sharding/
--
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]
