Thanks for this, We considering this approach - writing all the entries to some table V, and then updating a separate token cache T with a signal, picked up by the continuous query, which then filters the underlying V records, transforms them and sends them to the client.
However, one problem we ran into - is we lose the "old" values from the underlying table V. Normally the continuous query has access to the new value and the old value, so the client app can detect which entries no longer match the remote filter. With this technique however, the continuous query remote transformer has the old and new value of T, but is ultimately doing a ScanQuery on V to get all the "current" values. Do you have any advice on how we can still achieve that? -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/
