a. Actually, I'm looking at the code and in doubts now. Did you make any experiments? What do they show? b. Correct. sql() method goes directly to Ignite bypassing Spark and this is basically the same as calling IgniteCache.query(). c. savePairs() is a distributed operation on a Spark cluster, so this will not work. To use transactions you will have to use Ignite API.
To be honest, I'm not quite sure you should use IgniteRDD because it sounds like your use case is bigger than that (indexed SQL, transactions, etc.). Did you consider using pure Ignite API without integrating it with Spark? -Val -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Apache-Spark-Ignite-Integration-tp8556p9062.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.
