Hello Wolfram, After some reflection, it doesn't clear to me that this behavior is a bug. SQL engine always works with binary objects. When some operation (insert, update etc) is executed via SQL api, you can think about it as using something like the following: cache.withKeepBinary().query(...) In that case, it is assumed the code should be able to work with BinaryObject instances. So, it looks like CacheInterceptor should be implemented in a way that will allow handling both cases - BinaryObject and MemcachedEntry.
Best regards, Slava. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/
