After many tests, I found that if I first set up an Ignite client node and
then use ("jdbc:ignite:thin://127.0.0.1/") as the JDBC connection URL,
various problems will occur, but if similar (
"jdbc:ignite:thin://192.168.0.138/") The pure JDBC method that connects
directly to the target Ignite cluster will not cause problems. The sample
code for the problem is as follows:-- Sent from: http://apache-ignite-users.70518.x6.nabble.com/
