[GitHub] [shardingsphere] 90yangkang commented on issue #25903: Mysql Database field inconsistent。

["90yangkang (via GitHub)" <gi...@apache.org>]

90yangkang commented on issue #25903:
URL: https://github.com/apache/shardingsphere/issues/25903#issuecomment-1571296789

   > Hi @90yangkang , could you submit issue with [template](https://raw.githubusercontent.com/apache/shardingsphere/master/.github/ISSUE_TEMPLATE/bug-report.md)? e.g. ShardingSphere configuration etc
   
   configuration  info :
   config-sharding.yaml info：
   
   databaseName: db_mall
   dataSources:
     db1:
       url: jdbc:mysql://localhost:3306/db1
       username: root
       password: root
       connectionTimeoutMilliseconds: 30000
       idleTimeoutMilliseconds: 60000
       maxLifetimeMilliseconds: 1800000
       maxPoolSize: 50
       minPoolSize: 1
     db2:
       url: jdbc:mysql://localhost:3306/db2
       username: root
       password: root
       connectionTimeoutMilliseconds: 30000
       idleTimeoutMilliseconds: 60000
       maxLifetimeMilliseconds: 1800000
       maxPoolSize: 50
       minPoolSize: 1
     db3:
       url: jdbc:mysql://localhost:3306/db3
       username: root
       password: root
       connectionTimeoutMilliseconds: 30000
       idleTimeoutMilliseconds: 60000
       maxLifetimeMilliseconds: 1800000
       maxPoolSize: 50
       minPoolSize: 1
   
   rules:
   - !SHARDING
     defaultDatabaseStrategy:
       none:
     defaultTableStrategy:
       none:
   
   server.yaml  info：
   
   mode:
     type: Cluster
     repository:
       type: ZooKeeper
       props:
         namespace: db_mall_
         server-lists: 1.1.1.1:2181
         retryIntervalMilliseconds: 500
         timeToLiveSeconds: 60
         maxRetries: 3
         operationTimeoutMilliseconds: 500
     overwrite: true
   
   rules:
     - !AUTHORITY
       users:
         - root@%:root
         - sharding@:sharding
       provider:
         type: ALL_PERMITTED
     - !TRANSACTION
       defaultType: LOCAL
       # When the provider type is Narayana, the following properties can be configured or not
     - !SQL_PARSER
       sqlCommentParseEnabled: true
       sqlStatementCache:
         initialCapacity: 2000
         maximumSize: 65535
       parseTreeCache:
         initialCapacity: 128
         maximumSize: 1024
   
   props:
     max-connections-size-per-query: 1
     kernel-executor-size: 16  # Infinite by default.
     proxy-frontend-flush-threshold: 128  # The default value is 128.
     proxy-hint-enabled: true
     sql-show: false
     check-table-metadata-enabled: false
     show-process-list-enabled: false
       # Proxy backend query fetch size. A larger value may increase the memory usage of ShardingSphere Proxy.
       # The default value is -1, which means set the minimum value for different JDBC drivers.
     proxy-backend-query-fetch-size: -1
     check-duplicate-table-enabled: false
     proxy-frontend-executor-size: 0 # Proxy frontend executor size. The default value is 0, which means let Netty decide.
       # Available options of proxy backend executor suitable: OLAP(default), OLTP. The OLTP option may reduce time cost of writing packets to client, but it may increase the latency of SQL execution
       # and block other clients if client connections are more than `proxy-frontend-executor-size`, especially executing slow SQL.
     proxy-backend-executor-suitable: OLAP
     proxy-frontend-max-connections: 0 # Less than or equal to 0 means no limitation.
     sql-federation-enabled: false
       # Available proxy backend driver type: JDBC (default), ExperimentalVertx
     proxy-backend-driver-type: JDBC
     proxy-mysql-default-version: 5.7.18 # In the absence of schema name, the default version will be used.
     proxy-default-port: 3307 # Proxy default port.
     proxy-netty-backlog: 1024 # Proxy netty backlog.


-- 
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: notifications-unsubscribe@shardingsphere.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org