If you adjust your data model to be a more traditional 1:M relationship it would Just Work.
But you still don’t have to do it on the client side. If you use ignite.compute().broadcast(…) you can send the query out to your cluster, have the scans happen on the server side and only send the filtered results to the client. It’s still going to involve a full scan, however. Regards, Stephen > On 23 Oct 2018, at 16:34, the_palakkaran <[email protected]> wrote: > > Hi, > > My cache is like : key vs list of models. (key, ArrayList) > > I know that we have ScanQuery to apply filter conditions on keys. Is there a > provision to apply this on values against a particular key at ignite server > node? > > Otherwise I will have to pull these list of values to my client side and > apply filter. Any way to bypass? > > > > -- > Sent from: http://apache-ignite-users.70518.x6.nabble.com/
