This is an automated email from the ASF dual-hosted git repository.

menghaoran pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/shardingsphere.git


The following commit(s) were added to refs/heads/master by this push:
     new 6dfe9d9551b Compatible with COMPLEX_INLINE 
allow-range-query-with-inline-sharding for pipeline (#36524)
6dfe9d9551b is described below

commit 6dfe9d9551bec387c35cada8a7f4362f18b2d0b9
Author: Hongsheng Zhong <[email protected]>
AuthorDate: Thu Sep 11 16:59:40 2025 +0800

    Compatible with COMPLEX_INLINE allow-range-query-with-inline-sharding for 
pipeline (#36524)
---
 .../pipeline/sharding/ShardingPipelineYamlRuleConfigurationReviser.java | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git 
a/kernel/data-pipeline/feature/sharding/src/main/java/org/apache/shardingsphere/data/pipeline/sharding/ShardingPipelineYamlRuleConfigurationReviser.java
 
b/kernel/data-pipeline/feature/sharding/src/main/java/org/apache/shardingsphere/data/pipeline/sharding/ShardingPipelineYamlRuleConfigurationReviser.java
index fe27538f641..a7645d7a7c1 100644
--- 
a/kernel/data-pipeline/feature/sharding/src/main/java/org/apache/shardingsphere/data/pipeline/sharding/ShardingPipelineYamlRuleConfigurationReviser.java
+++ 
b/kernel/data-pipeline/feature/sharding/src/main/java/org/apache/shardingsphere/data/pipeline/sharding/ShardingPipelineYamlRuleConfigurationReviser.java
@@ -35,7 +35,7 @@ public final class 
ShardingPipelineYamlRuleConfigurationReviser implements Pipel
     
     private void enableRangeQueryForInline(final YamlShardingRuleConfiguration 
yamlRuleConfig) {
         for (YamlAlgorithmConfiguration each : 
yamlRuleConfig.getShardingAlgorithms().values()) {
-            if ("INLINE".equalsIgnoreCase(each.getType())) {
+            if ("INLINE".equalsIgnoreCase(each.getType()) || 
"COMPLEX_INLINE".equalsIgnoreCase(each.getType())) {
                 each.getProps().put("allow-range-query-with-inline-sharding", 
Boolean.TRUE.toString());
             }
         }

Reply via email to