Hi Val - There are a few more potential issues we noticed when using Spi indexing in 1.5.0.final:
- method query() in IndexingSpi interface returns Iterator<Cache.Entry<?,?>> but elements of type Map.Entry are expected further down the stack (i.e. in IgniteCacheProxy:528). We had to create type that extends both Map.Entry and Cache.Entry to get it working. - when IndexingSpi.store() throws an exception on commit, error is not propagated to a client node and transaction ends up with state COMMITTED as if no error occured. In a server node transaction state gets marked as UNKNOWN though. - setters in SpiQuery return SqlQuery type (rather than SpiQuery) which means they can't be used in method chaining manner Kamil -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/SpiQuery-fails-with-exception-tp3615p3626.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.
