On Mon, Feb 9, 2015 at 9:17 PM, Valentin Kulichenko < [email protected]> wrote:
> Guys, > > I'm going to start refactoring of continuous queries shortly and I've got > several question on new API. > > 1. What's the purpose of ContinuousQuery.setInitialFilter(..) method? > Initial filter is used for iteration through cache at the point of creation of continuous queries. If it is set, then continuous query should iterate through all cache entries and return entries that pass the filter. > 2. In current implementation local listener returns boolean flag which > defines whether to continue listening or not. > javax.cache.event.CacheEntryUpdatedListener > returns void, so these feature will be dropped. Are we OK with that? > I think it is OK, as long as the query can be canceled from the node that started it (or any other node for that matter). > 3. There is no cursor for continuous query, so what should be retuned > from IgniteCache.query(..) method? Is null OK? > No, not OK. If "initialFilter()" is set, then cursor should be returned. Otherwise, null should be returned. > > Can anyone clarify? > > Thanks! > -- > Val > > On Thu, Feb 5, 2015 at 2:04 AM, Yakov Zhdanov <[email protected]> > wrote: > > > Is this what you asking for > > - org.apache.ignite.cache.query.QueryContinuousPredicate? I think you can > > get entire idea from this. > > > > -- > > Yakov Zhdanov, Director R&D > > *GridGain Systems* > > www.gridgain.com > > > > 2015-02-05 6:58 GMT+03:00 Valentin Kulichenko < > > [email protected] > > >: > > > > > Hi! > > > > > > Anyone knows where I can find new API for continuous queries? > > > > > > https://issues.apache.org/jira/browse/IGNITE-143 doesn't mention > > anything > > > about it. > > > > > > Thanks! > > > > > >
