xcmonline edited a comment on issue #14543:
URL: 
https://github.com/apache/shardingsphere/issues/14543#issuecomment-1007106240


   only setting.
   server.ymal
   
   ```
   mode:
     type: Cluster
     repository:
       type: Zookeeper
       props:
         namespace: qiyun_db1
         server-lists: localhost:2181
     overwrite: true
   rules:
     - !AUTHORITY
       users:
         - root@%:123456
       provider:
         type: ALL_PRIVILEGES_PERMITTED
   props:
     max-connections-size-per-query: 1
     kernel-executor-size: 16
     proxy-frontend-flush-threshold: 128
     proxy-opentracing-enabled: false
     proxy-hint-enabled: false
     sql-show: false
     check-table-metadata-enabled: false
   ```
   
   
   and 
   
   config-sharding.yaml
   
   ```
   schemaName: testdb
   dataSources:
     ds_0:
       url: jdbc:mysql://127.0.0.1:3306/test?serverTimezone=UTC&useSSL=false
       username: root
       password: xxxxxx
       connectionTimeoutMilliseconds: 30000
       idleTimeoutMilliseconds: 60000
       maxLifetimeMilliseconds: 1800000
       maxPoolSize: 50
       minPoolSize: 1
   rules:
   - !SHARDING
     tables:
       obs_aws_data_min:
         actualDataNodes: ds_0.obs_aws_data_min_${0..1}
         tableStrategy:
           standard:
             shardingColumn: observ_time
             shardingAlgorithmName: sharding_by_time
         keyGenerateStrategy:
           column: id
           keyGeneratorName: snowflake
     defaultDatabaseStrategy:
       none:
     defaultTableStrategy:
       none:
     shardingAlgorithms:
       sharding_by_time:
         type: auto_interval
         props:
           datetime-lower: "2020-10-01 00:00:00"
           sharding-seconds: "86400"
           datetime-upper: "2020-10-05 00:00:00"
     keyGenerators:
       snowflake:
         type: SNOWFLAKE
         props:
           worker-id: 123
   ```
   
   


-- 
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]


Reply via email to