Hi, to clarify: 1) Thin client works fine 2) Thick client using port 11211 works fine 3) The "Client Node" connection is the one that was not working.
I got the Client Node connection (#3) to work by specifying the cache name in the connection string. Now it connects, and all SQL works well. I thought that this was fixed already in 2.6, so that you didn't have to specify the cache name anymore? In any case, it works. The next problem that I ran into: executing scala code (using %ignite) makes the entire Ignite interpreter in Zeppelin hang, without any errors in logs. How do I debug this? -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/
