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

   ## 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?
   
   5.4.1
   
   ### Which project did you use? ShardingSphere-JDBC or ShardingSphere-Proxy?
   
   ShardingSphere-JDBC
   
   ### Expected behavior
   
   I want to print SQL. Follow the documentation to change the yaml 
configuration from false to true, but not working.
   `props:
     sql-show: true`
   
   ### Actual behavior
   
   SQL log is not printed
   
   ### Reason analyze (If you can)
   
   
![image](https://github.com/apache/shardingsphere/assets/45219837/0e97b23b-4fe1-4b3a-b6d0-8f1a09e48e33)
   
   The configuration in zookeeper is used first, and the modification of the 
local yaml file not working.
   I'm not sure if this is a BUG, I'm new to shardingsphere. After debugging, 
the problem of SQL logs not being printed was solved, which took a while.
   
   ### Steps to reproduce the behavior, such as: SQL to execute, sharding rule 
configuration, when exception occur etc.
   
   on first startup,sql-show: false;
   Modify sql-show: true and restart the service;
   SQL is not printed.
   
   ### 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