In case the performance of a fix rate is appropriate for you I think your solution make sense because it is very simple and robust.
Also, you can use IgniteScheduler ( https://ignite.apache.org/releases/mobile/org/apache/ignite/IgniteScheduler.html) instead of spring scheduler. On Wed, Dec 14, 2016 at 9:22 PM, begineer <[email protected]> wrote: > Thanks for reply first of all. Well I had this in back of my mind but it > will > be like duplicating the data which we already have in other cache(trades > cache which I am currently querying). > > So other way I can think of is using spring scheduler with 1 minute > fix-rate > and check if any item moved to SUCCESS state, if yes, postpone execution by > one minute(something like fix-delay but this works after executing the job, > but my requirement is it should delay the execution itself.) > > If no more items moved to final state within mentioned time, we execute the > scheduler. > > Any suggestions in this approach please or any better one? > > > > -- > View this message in context: http://apache-ignite-users. > 70518.x6.nabble.com/Detecting-terminal-condition-for-group- > of-items-in-Ignite-cache-tp9526p9539.html > Sent from the Apache Ignite Users mailing list archive at Nabble.com. >
