448700174 commented on issue #29421:
URL:
https://github.com/apache/shardingsphere/issues/29421#issuecomment-1858729629
I have tried the 5.4.1, But it cannot execute correctly even a simple
SQL.
And My configuration on 5.4.1 is as follows:
mode: # 不配置默认单机
type: Standalone # 运行模式类型。可选配置：Standalone、Cluster
repository:
type: JDBC # 持久化仓库类型
props:
sql-show: true
databaseName: yb_test
dataSources:
ds:
dataSourceClassName: com.zaxxer.hikari.HikariDataSource
driverClassName: com.mysql.cj.jdbc.Driver
jdbcUrl:
jdbc:mysql://192.168.3.227:3306/yb_test?allowMultiQueries=true&serverTimezone=GMT%2B8&characterEncoding=utf-8
username: localdev
password: M42-7Z7f
minimumIdle: 2
idleTimeoutMilliseconds: 600000
maxPoolSize: 10
minPoolSize: 1
autoCommit: true
poolName: MyHikariCP
maxLifetimeMilliseconds: 1800000
connectionTimeout: 30000
connectionTestQuery: SELECT 1
rules:
- !SINGLE
tables:
- "*.*"
- !SHARDING
shardingAlgorithms:
tenant_id_sharding:
type: CLASS_BASED
props:
strategy: standard
algorithmClassName:
com.youban.medical.TenantIdShardingAlgorithm
bindingTables:
-
medical_advice,medical_advice_main,medical_advice_group,medical_advice_item,medical_advice_dispense,medical_advice_settle,medical_advice_settle_item
-
medical_ward_schedule,medical_ward_record,medical_ward_abnormal
-
medical_medicine_kit_order,medical_medicine_kit_order_item
-
medical_chronic_follow,medical_chronic_data,medical_device_data,medical_device_alarm
tables:
medical_advice:
actualDataNodes: ds.medical_advice_$->{1..99}
tableStrategy:
standard:
shardingColumn: tenant_id
shardingAlgorithmName:
tenant_id_sharding
medical_advice_main:
actualDataNodes:
ds.medical_advice_main$->{1..99}
tableStrategy:
standard:
shardingColumn: tenant_id
shardingAlgorithmName:
tenant_id_sharding
medical_advice_group:
actualDataNodes:
ds.medical_advice_group$->{1..99}
tableStrategy:
standard:
shardingColumn: tenant_id
shardingAlgorithmName:
tenant_id_sharding
medical_advice_item:
actualDataNodes:
ds.medical_advice_item$->{1..99}
tableStrategy:
standard:
shardingColumn: tenant_id
shardingAlgorithmName:
tenant_id_sharding
medical_advice_dispense:
actualDataNodes:
ds.medical_advice_dispense$->{1..99}
tableStrategy:
standard:
shardingColumn: tenant_id
shardingAlgorithmName:
tenant_id_sharding
medical_advice_settle:
actualDataNodes:
ds.medical_advice_settle$->{1..99}
tableStrategy:
standard:
shardingColumn: tenant_id
shardingAlgorithmName:
tenant_id_sharding
medical_advice_settle_item:
actualDataNodes:
ds.medical_advice_settle_item$->{1..99}
tableStrategy:
standard:
shardingColumn: tenant_id
shardingAlgorithmName:
tenant_id_sharding
medical_ward_schedule:
actualDataNodes:
ds.medical_ward_schedule$->{1..99}
tableStrategy:
standard:
shardingColumn: tenant_id
shardingAlgorithmName:
tenant_id_sharding
medical_ward_record:
actualDataNodes:
ds.medical_ward_record$->{1..99}
tableStrategy:
standard:
shardingColumn: tenant_id
shardingAlgorithmName:
tenant_id_sharding
medical_ward_abnormal:
actualDataNodes:
ds.medical_ward_abnormal$->{1..99}
tableStrategy:
standard:
shardingColumn: tenant_id
shardingAlgorithmName:
tenant_id_sharding
medical_medicine_kit_order:
actualDataNodes:
ds.medical_medicine_kit_order$->{1..99}
tableStrategy:
standard:
shardingColumn: tenant_id
shardingAlgorithmName:
tenant_id_sharding
medical_medicine_kit_order_item:
actualDataNodes:
ds.medical_medicine_kit_order_item$->{1..99}
tableStrategy:
standard:
shardingColumn: tenant_id
shardingAlgorithmName:
tenant_id_sharding
medical_chronic_follow:
actualDataNodes:
ds.medical_chronic_follow$->{1..99}
tableStrategy:
standard:
shardingColumn: tenant_id
shardingAlgorithmName:
tenant_id_sharding
medical_chronic_data:
actualDataNodes:
ds.medical_chronic_data$->{1..99}
tableStrategy:
standard:
shardingColumn: tenant_id
shardingAlgorithmName:
tenant_id_sharding
medical_device_data:
actualDataNodes:
ds.medical_device_data$->{1..99}
tableStrategy:
standard:
shardingColumn: tenant_id
shardingAlgorithmName:
tenant_id_sharding
medical_device_alarm:
actualDataNodes:
ds.medical_device_alarm$->{1..99}
tableStrategy:
standard:
shardingColumn: tenant_id
shardingAlgorithmName:
tenant_id_sharding
------------------ 原始邮件 ------------------
发件人:
"apache/shardingsphere"
***@***.***>;
发送时间: 2023年12月16日(星期六) 上午8:30
***@***.***>;
***@***.******@***.***>;
主题: Re: [apache/shardingsphere] Can not get all columns when join table
(Issue #29421)
Hi @448700174, can you try the latest version 5.4.1? I think this problem
has been solved.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.Message ID: ***@***.***>
--
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]
