Thanks for the prompt reply, Val. In short, I need a continuous SqlListQuery, but it looks like that is not supported by Ignite at the moment. We have a cache that consists of lots of rows and columns and we need to extract a list of unique values for only a handful of fields. We would like to use SqlListQuery because we're not interested in the entire rows (which consist of 50+ fields in our case). We are using continuous queries to stream updates to the client side (the continuous query is triggered by the initial client request, not at start-up). I already looked at some of the internal Ignite code, and it seems that type conformance to Query<Cache.Entry<K, V>> is only a superficial problem. Providing a custom implementation of that interface will not solve my issue. The real problem is that there is code in Ignite that performs instanceof checks for specific query implementations (e.g., in IgniteCacheProxy), which means that Ignite only supports query implementations that it knows. So, my initial query wrapper idea is off the table. Do you have another suggestion how we can execute continuous SQL queries that do not return complete cache rows but only a few specific fields?
-- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Continuous-SqlListQuery-tp671p680.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.
