Hi, IgniteRDD is useful when you already have a Spark application and want to use Ignite as an underlying storage to share the state between different Spark jobs (which is not possible with plain Spark) and to get advantage of fast indexed SQL queries provided by Ignite (there are no indexes in Spark).
IgniteRDD provides full RDD API, but cache API is limited. For example, it doesn't expose transactions. If you're creating an application from scratch, I would recommend to use Ignite API directly with all its features (cache, compute, streaming, etc.). Makes sense? -Val -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Downsides-of-Spark-Ignite-for-extended-cache-management-and-access-tp5154p5188.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.
