[MTCGA]: new failures in builds [6094982] needs to be handled

Hi Igniters, I've detected some new issue on TeamCity to be handled. You are more than welcomed to help. *Test with high flaky rate in master ZookeeperDiscoverySegmentationAndConnectionRestoreTest.testSegmentation3 https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8&te

[MTCGA]: new failures in builds [6101840] needs to be handled

Hi Igniters, I've detected some new issue on TeamCity to be handled. You are more than welcomed to help. *New Critical Failure in master Cache (Restarts) 1 https://ci.ignite.apache.org/buildConfiguration/IgniteTests24Java8_CacheRestarts1?branch=%3Cdefault%3E No changes in the build

[MTCGA]: new failures in builds [6101850] needs to be handled

Hi Igniters, I've detected some new issue on TeamCity to be handled. You are more than welcomed to help. *New test failure in master IgniteTopologyValidatorGridSplitCacheTest.testTopologyValidatorWithCacheGroup https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8&testNa

Re: Apache Ignite 3 Alpha 2 webinar follow up questions

Something else came to mind, are there plans to support prepared queries? I recall someone saying before that Ignite does internally cache queries but it's not at all clear if or how it does do that. I assume a simple hash of the query isn't enough. We generate SQL queries based on user runtime s