cobstergo opened a new issue #6856:
URL: https://github.com/apache/shardingsphere/issues/6856
before we use sharding proxy 4.1.1 version , we has sharding config
(config-sharding.yaml) like this:
schemaName: order
dataSources:
ds_0:
url:
jdbc:mysql://xxxxxxxxx:3306/order?useAffectedRows=true&characterEncoding=UTF-8&autoReconnect=true&autoReconnectForPools=true&useSSL=false
username:
password:
connectionTimeoutMilliseconds: 30000
idleTimeoutMilliseconds: 60000
maxLifetimeMilliseconds: 1800000
maxPoolSize: 1000
shardingRule:
tables:
t_order:
actualDataNodes: ds_0.t_order20200$->{1..9},ds_0.t_order20201$->{0..2}
tableStrategy:
standard:
shardingColumn: firstTime
**preciseAlgorithmClassName:
shardingproxyalgorithm.sharding.order.ShardingTableByMonthAlgorithmPrecise
rangeAlgorithmClassName:
shardingproxyalgorithm.sharding.order.ShardingTableByMonthAlgorithmRange**
**keyGenerator:
type: SELFGROWING
column: id**
bindingTables:
- t_order
and we try use master branch version 5.0.0 , we find it looks like
config-sharding.yaml has changed.
schemaName: order
dataSourceCommon:
username:
password:
connectionTimeoutMilliseconds: 120000
idleTimeoutMilliseconds: 60000
maxLifetimeMilliseconds: 1800000
maxPoolSize: 10000
minPoolSize: 1000
maintenanceIntervalMilliseconds: 30000
dataSources:
ds_0:
url:
jdbc:mysql://xxxxxxxxx:3306/order?useAffectedRows=true&characterEncoding=UTF-8&autoReconnect=true&autoReconnectForPools=true&useSSL=false
rules:
tables:
t_order:
actualDataNodes: ds_0.t_order20200$->{1..9},ds_0.t_order20201$->{0..2}
**tableStrategy:
standard:
shardingColumn: firstTime
shardingAlgorithmName: shardingByMonth(???)**
**keyGenerateStrategy:
column: id
keyGeneratorName: SELFGROWING(???)**
bindingTables:
- t_order
defaultTableStrategy:
none:
**shardingAlgorithms:
shardingByMonth:
type: INLINE (???)
props:
algorithm.expression:(???)**
so we don't konw how to config self shardingAlgorithm and self
ShardingKeyGenerator in 5.0.0. cloud you help me?
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
[email protected]
