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

   ## Bug Report
   
   **For English only**, other languages will not accept.
   
   Before report a bug, make sure you have:
   
   - Searched open and closed [GitHub 
issues](https://github.com/apache/shardingsphere/issues).
   - Read documentation: [ShardingSphere 
Doc](https://shardingsphere.apache.org/document/current/en/overview).
   
   Please pay attention on issues you submitted, because we maybe need more 
details. 
   If no response anymore and we cannot reproduce it on current information, we 
will **close it**.
   
   Please answer these questions before submitting your issue. Thanks!
   
   ### Which version of ShardingSphere did you use?
   we find java version: java8, full_version=1.8.0_282
   ShardingSphere-5.1.3-SNAPSHOT
   Commit ID: 7c67365b394d2e3ac562329b550c135c31ea764d
   Commit Message: Avoid overhead of invoking method in Optional.orElse (#18921)
   Branch: 7c67365b394d2e3ac562329b550c135c31ea764d
   Build time: 2022-07-08T19:24:17+0800
   
   ### Which project did you use? ShardingSphere-JDBC or ShardingSphere-Proxy?
   ShardingSphere-Proxy
   
   ### Expected behavior
   Label related distsql syntax is not supported
   ### Actual behavior
   Label related distsql syntax is supported
   ### Reason analyze (If you can)
   
   ### Steps to reproduce the behavior, such as: SQL to execute, sharding rule 
configuration, when exception occur etc.
   -- 新增
   LABEL INSTANCE xxxx with olap,group_by;
   -- 全部移除
   UNLABEL INSTANCE xxxx ;
   -- 部分移除
   UNLABEL INSTANCE xxxx with group_by;
   -- 部分增加(原有基础上新增)
   LABEL INSTANCE xxxx  with new_label;
   -- 重定义(完全覆盖原有的)
   RELABEL INSTANCE xxxx  with label_0, label_1;
   ### Example codes for reproduce this issue (such as a github link).
   


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