pengzhiming-sys commented on issue #7067:
URL: https://github.com/apache/shardingsphere/issues/7067#issuecomment-680417191


   The proxy service can be normal, but an error occurs when executing SQL 
through the client
   The server.yaml and config-sharding.yaml configuration files are all 
configured as follows:
   authentication:
     users:
       root:
         password: root
       sharding:
         password: sharding 
         authorizedSchemas: sharding_pg
   
   props:
     max.connections.size.per.query: 1
     acceptor.size: 16  # The default value is available processors count * 2.
     executor.size: 16  # Infinite by default.
     proxy.frontend.flush.threshold: 128  # The default value is 128.
     proxy.transaction.type: LOCAL
     proxy.opentracing.enabled: false
     proxy.hint.enabled: false
     query.with.cipher.column: true
     sql.show: false
     allow.range.query.with.inline.sharding: false
   
   
   schemaName: sharding_pg
   
   dataSources:
     ds_0:
       url: 
jdbc:postgresql://172.22.2.21:5432/o3test?currentSchema=public&serverTimezone=UTC&useSSL=false
       username: poc_cnoss_sub
       password: poc_cnoss_sub
       connectionTimeoutMilliseconds: 30000
       idleTimeoutMilliseconds: 60000
       maxLifetimeMilliseconds: 1800000
       maxPoolSize: 50
     ds_1:
       url: 
jdbc:postgresql://172.22.2.21:5432/itsp?currentSchema=public&serverTimezone=UTC&useSSL=false
       username: poc_cnoss_sub
       password: poc_cnoss_sub
       connectionTimeoutMilliseconds: 30000
       idleTimeoutMilliseconds: 60000
       maxLifetimeMilliseconds: 1800000
       maxPoolSize: 50
   
   shardingRule:
     tables:
       lab_labelcatalog:
         actualDataNodes: ds_${0..1}.lab_labelcatalog_${0}
         databaseStrategy:
           inline:
             shardingColumn: catalogId
             algorithmExpression: ds_${catalogId % 2}
         tableStrategy:
           inline:
             shardingColumn: uuid
             algorithmExpression: lab_labelcatalog_${uuid % 2}
   
   


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


Reply via email to