Hello! Currently, the only way to do efficient parent-child join is SQL since it has secondary indexes. I guess you need to trigger SQL from continuous query.
Regards, -- Ilya Kasnacheev пн, 11 янв. 2021 г. в 14:44, Goncalo Carvalho <[email protected]>: > Hi, > > I'm looking for advice on what is currently possible in terms of using > continuous queries. > > We're developing a server application that makes use of several joins > (using SqlFieldsQuery) across several caches to return results. > > We'd like to be able to implement some means to return (asynchronously) > updates to clients if the caches get updated. > Continuous queries allow us to listen to updates but we can't really run > our sql within them. We'd need to react to an update with an extra > SqlFieldsQuery (after we listened to the update). > > There was some discussion about implementing materialised views, > > > http://apache-ignite-developers.2346864.n4.nabble.com/Using-materialised-views-for-queries-with-joins-td35197.html > > although it doesn't appear to have had any traction. > > Is there a best way of doing this? We can issue our query periodically or > do the above two-step process but we're just trying to understand if > there's something else we should consider. > > Kind regards, > > Goncalo > >
