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

   ## Feature Request
   
   **For English only**, other languages will not be accepted.
   
   Please pay attention on issues you submitted, because we maybe need more 
details. 
   If no response anymore and we cannot make decision by current information, 
we will **close it**.
   
   Please answer these questions before submitting your issue. Thanks!
   
   ### Is your feature request related to a problem?
   
   - See https://github.com/apache/shardingsphere/pull/37401 .
   
   ### Describe the feature you would like.
   
   - According to tests at https://github.com/apache/shardingsphere/pull/37401 
and https://github.com/ClickHouse/clickhouse-java/issues/2636, the integration 
tests on ShardingSphere's master branch using 
`com.clickhouse:clickhouse-jdbc:0.6.3:http` cannot connect to clickhouse-server 
`25.10.1+`. To fix the integration tests, you need to switch 
`com.clickhouse:clickhouse-jdbc:0.6.3:http` to 
`com.clickhouse:clickhouse-jdbc:0.9.4:all`.
   - This essentially means switching the ClickHouse JDBC Driver from V1 to V2. 
A significant change is that ClickHouse JDBC Driver V2 introduces 
`org.antlr:antlr4-maven-plugin:4.13.2` to parse SQL, which is documented at 
https://shardingsphere.apache.org/document/current/en/user-manual/shardingsphere-jdbc/optional-plugins/clickhouse/#limitations-of-clickhouse-jdbc-driver-v2
 .
   - <img width="2792" height="1472" alt="Image" 
src="https://github.com/user-attachments/assets/7d9fbb3e-66b7-48c3-b598-2bc4595dcb95";
 />
   - To fix the integration issues with clickhouse-server `25.10.1+`, it's 
actually necessary to update `org.antlr:antlr4-runtime` on the ShardingSphere 
side to `4.13.2`.
   


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