As I understand, Ignite has two completely disconnected features - write-through/read-through caching and SQL. If SQL fetched what's not currently cached in memory from the cache store that would solve the problem. This is only one possible solution and it covers only the sources described/cached by Ignite caches. It's also possible to add an API to expose external sources to SQL without threading it through an Ignite cache (something like external rdbms tables, Presto plugin, etc.). Any plans to implement either of the two or anything equivalent? Thanks.
-- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/External-data-sources-tp11766p11829.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.
