marker-wu commented on issue #13632:
URL: 
https://github.com/apache/shardingsphere/issues/13632#issuecomment-970156626


   > Some verification:
   > 
   > 1. Are you running version `5.0.0`?
      yes
   > 2. Could you paste your current schema rules and rule cache? Register 
center (e.g. ZooKeeper) path example: `/metadata/sharding_db/rules`, 
`/metadata/sharding_db/rules/cache/xxx`.
   
   
   /metadata/sharding_db/rules:
   - !SHARDING
     bindingTables:
     - t_order,t_order_item
     defaultDatabaseStrategy:
       standard:
         shardingAlgorithmName: database_inline
         shardingColumn: user_id
     defaultTableStrategy:
       none: ''
     keyGenerators:
       snowflake:
         props:
           worker-id: 123
         type: SNOWFLAKE
     shardingAlgorithms:
       database_inline:
         props:
           algorithm-expression: ds_${user_id % 2}
         type: INLINE
       t_order_inline:
         props:
           algorithm-expression: t_order_${order_id % 2}
         type: INLINE
       t_order_item_inline:
         props:
           algorithm-expression: t_order_item_${order_id % 2}
         type: INLINE
     tables:
       t_order:
         actualDataNodes: ds_${0..1}.t_order_${0..1}
         keyGenerateStrategy:
           column: order_id
           keyGeneratorName: snowflake
         logicTable: t_order
         tableStrategy:
           standard:
             shardingAlgorithmName: t_order_inline
             shardingColumn: order_id
       t_order_item:
         actualDataNodes: ds_${0..1}.t_order_item_${0..1}
         keyGenerateStrategy:
           column: order_item_id
           keyGeneratorName: snowflake
         logicTable: t_order_item
         tableStrategy:
           standard:
             shardingAlgorithmName: t_order_item_inline
             shardingColumn: order_id
   
   
   /metadata/sharding_db/rules/cache/0a81aa01235c42738b80eda6ad3dd0ec:
   
   - !SHARDING
     bindingTables:
     - t_order,t_order_item
     defaultDatabaseStrategy:
       standard:
         shardingAlgorithmName: database_inline
         shardingColumn: user_id
     defaultTableStrategy:
       none: ''
     keyGenerators:
       snowflake:
         props:
           worker-id: 123
         type: SNOWFLAKE
       t_order_snowflake:
         props:
           worker-id: '123'
         type: snowflake
       t_order_item_snowflake:
         props:
           worker-id: '124'
         type: snowflake
     shardingAlgorithms:
       database_inline:
         props:
           algorithm-expression: ds_${user_id % 2}
         type: INLINE
       t_order_inline:
         props:
           algorithm-expression: t_order_${order_id % 2}
         type: INLINE
       t_order_item_inline:
         props:
           algorithm-expression: t_order_item_${order_id % 2}
         type: INLINE
       scaling_inline:
         props:
           algorithm-expression: t_order_${order_id % 3} +2
         type: inline
     tables:
       t_order:
         actualDataNodes: ds_${2..4}.t_order${0..1}
         databaseStrategy:
           standard:
             shardingAlgorithmName: scaling_inline
             shardingColumn: user_id
         keyGenerateStrategy:
           column: order_id
           keyGeneratorName: t_order_snowflake
         logicTable: t_order
         tableStrategy:
           standard:
             shardingAlgorithmName: t_order_inline
             shardingColumn: order_id
       t_order_item:
         actualDataNodes: ds_${2..4}.t_order_item_${0..1}
         databaseStrategy:
           standard:
             shardingAlgorithmName: scaling_inline
             shardingColumn: user_id
         keyGenerateStrategy:
           column: order_item_id
           keyGeneratorName: t_order_item_snowflake
         logicTable: t_order_item
         tableStrategy:
           standard:
             shardingAlgorithmName: t_order_item_inline
             shardingColumn: order_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]


Reply via email to