DengQin commented on issue #33339:
URL: 
https://github.com/apache/shardingsphere/issues/33339#issuecomment-2426692143

   sharding config:
   
   rules:
     # 单表
     - !SINGLE
       tables:
         - ds-marketing.*
       defaultDataSource: ds-marketing
   
     # 分片配置
     - !SHARDING
       tables:
         t_benefit_distribute_record:
           actualDataNodes: ds-marketing.t_benefit_distribute_record_$->{0..15}
           tableStrategy:
             standard:
               shardingColumn: user_id
               shardingAlgorithmName: t_benefit_distribute_record_inline
        #   databaseStrategy:
         #    hint:
           #    shardingAlgorithmName: database_inline
               
         t_activity_submit_record:
           actualDataNodes: ds-marketing.t_activity_submit_record_$->{0..3}
           tableStrategy:
             standard:
               shardingColumn: user_info
               shardingAlgorithmName: t_activity_submit_record_inline
      #     databaseStrategy:
       #      hint:
        #       shardingAlgorithmName: database_inline
   
         t_activity_stock:
           actualDataNodes: ds-marketing.t_activity_stock_$->{0..7}
           tableStrategy:
             standard:
               shardingColumn: activity_id
               shardingAlgorithmName: t_activity_stock_inline
      #     databaseStrategy:
       #      hint:
        #       shardingAlgorithmName: database_inline
   
         t_activity_user_times:
           actualDataNodes: ds-marketing.t_activity_user_times_$->{0..7}
           tableStrategy:
             standard:
               shardingColumn: user_id
               shardingAlgorithmName: t_activity_user_times_inline
      #     databaseStrategy:
       #      hint:
        #       shardingAlgorithmName: database_inline
   
         t_raffle_winner_sub_log:
           actualDataNodes: ds-marketing.t_raffle_winner_sub_log_$->{0..19}
           tableStrategy:
             standard:
               shardingColumn: user_id
               shardingAlgorithmName: t_raffle_winner_sub_log_inline
     #      databaseStrategy:
       #      hint:
       #        shardingAlgorithmName: database_inline
   
         t_user_business_event:
           actualDataNodes: ds-marketing.t_user_business_event_$->{0..15}
           tableStrategy:
             standard:
               shardingColumn: business_id
               shardingAlgorithmName: t_user_business_event_inline
       #    databaseStrategy:
       #      hint:
       #        shardingAlgorithmName: database_inline
   
        
   
       defaultDatabaseStrategy:
         hint:
           shardingAlgorithmName: database_algorithm_inline
   
       shardingAlgorithms:
         database_inline:
           type: HINT_INLINE
           props:
             algorithm-expression: ds-marketing
   
         database_algorithm_inline:
           type: CLASS_BASED
           props:
             strategy: HINT
             algorithmClassName: comXXXX
   
   
         t_benefit_distribute_record_inline:
           type: INLINE
           props:
             algorithm-expression: t_benefit_distribute_record_$->{user_id % 16}
         t_activity_submit_record_inline:
           type: INLINE
           props:
             algorithm-expression: 
t_activity_submit_record_$->{Math.abs(user_info.hashCode()) % 4}
         t_activity_stock_inline:
           type: INLINE
           props:
             algorithm-expression: t_activity_stock_$->{activity_id % 8}
         t_activity_user_times_inline:
           type: INLINE
           props:
             algorithm-expression: t_activity_user_times_$->{user_id % 8}
         t_raffle_winner_sub_log_inline:
           type: INLINE
           props:
             algorithm-expression: t_raffle_winner_sub_log_$->{user_id % 20}
         t_user_business_event_inline:
           type: INLINE
           props:
             algorithm-expression: 
t_user_business_event_$->{Math.abs(business_id.hashCode()) % 16}
   
   props:
     sql-show: true
   
   


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