Hello! You could have secondary (SQL) index on time, and do SELECT ORDER BY time to get most eager hosts.
For initial time, you could 0L as default value. I.e. check for null => use 0L if null. Regards, -- Ilya Kasnacheev чт, 11 окт. 2018 г. в 0:20, matt <[email protected]>: > Thanks for the feedback, Ilya! > > In your example, where would the initial "host" in "long time = > cache.get(host);" come from? In the case I need to solve for, I would not > know what host would be most suitable to make a request to, so would need > to > continuously loop over all available keys until the crawl is done. This may > introduce a performance hit, if (for example) the only host that is ready > for a request is the last one in a very large list of keys. Does that make > sense? Apologies if I'm misunderstanding! > > - Matt > > > > -- > Sent from: http://apache-ignite-users.70518.x6.nabble.com/ >
