You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@shardingsphere.apache.org by "terrymanu (via GitHub)" <gi...@apache.org> on 2023/02/27 16:54:15 UTC

[GitHub] [shardingsphere] terrymanu opened a new issue, #24363: Redesign hierarchy of feature rules

terrymanu opened a new issue, #24363:
URL: https://github.com/apache/shardingsphere/issues/24363

   Currently, ShardingSphere uses order to control the creation and decoration of Feature Rules, which leads to mutual influence and dependence among different rules, and is not conducive to the plug-in design of rules.
   
   The new ShardingSphere Feature Rule scheme divides rules into hierarchical levels. Rules of different levels are constructed in the order of their levels, and rules of the same level do not need to be distinguished in order. The rule hierarchy is divided as follows:
   
   - MetaRule
     - Resource
       - Node(Instance)
         - DatabaseDiscoveryRule(Traffic)
       - Unit(DataSource)
         - ReadwriteSplitRule(Traffic)
     - Table
       - ShardingRule(Data + Traffic)
       - ShadowRule(Traffic)
     - Column
       - EncryptRule(Data)
       - MaskRule(Data)
   - OperationRule
     - AuthorityRule
   
   
   Construct order: 
   Resource -> Table -> Column
   
   Execute order:
   Table ->
   -- Traffic: Resource
   -- Data: Column


-- 
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.apache.org

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


[GitHub] [shardingsphere] boyjoy1127 commented on issue #24363: Redesign hierarchy of feature rules

Posted by "boyjoy1127 (via GitHub)" <gi...@apache.org>.
boyjoy1127 commented on issue #24363:
URL: https://github.com/apache/shardingsphere/issues/24363#issuecomment-1585969442

   Will this issue be completed before June 15 which is the final date of version 5.4.0?


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


[GitHub] [shardingsphere] github-actions[bot] commented on issue #24363: Redesign hierarchy of feature rules

Posted by "github-actions[bot] (via GitHub)" <gi...@apache.org>.
github-actions[bot] commented on issue #24363:
URL: https://github.com/apache/shardingsphere/issues/24363#issuecomment-1657254480

   There hasn't been any activity on this issue recently, and in order to prioritize active issues, it will be marked as stale.


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


Re: [I] Redesign hierarchy of feature rules [shardingsphere]

Posted by "github-actions[bot] (via GitHub)" <gi...@apache.org>.
github-actions[bot] commented on issue #24363:
URL: https://github.com/apache/shardingsphere/issues/24363#issuecomment-2023870746

   There hasn't been any activity on this issue recently, and in order to prioritize active issues, it will be marked as stale.


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