It is likely entries are being quickly produced and filling up the buffer
giving the effect of an immediate update.
You can test it via specific delays and logging.
Make the server print out the counter of the object.
say:
if the key is an integer and the value is too then print out the key as
This was what I thought, however, no matter what number I set to the
pageSize, e.g., 5, 20, 100, my local listener got the update immediately, 1
by 1, but not batching by the page size...
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
You are correct. Your local reciever will get an update every 100 entries.
setPageSize sets the number of entries to batch together before sending.
When the server has accumulated a number of entries larger than getPageSize
it sends a message to the receiver.
Like I mentioned before,
Thanks Alex,
But I still not quite understand the expected behaviour. If I set the page
size to 100 and interval to 0, should the local query be triggered for every
100 updates?
Regards,
Rick
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Hi,
setTimeInterval limits the time Ignite will wait for an internal buffer
to fill up before sending.
It is not a time delay setting.
From the doc:
https://ignite.apache.org/releases/latest/javadoc/org/apache/ignite/cache/query/ContinuousQuery.html#setTimeInterval-long-
When a
Dear all,
I tried to play around with the setPageSize and setTimeInterval on
Continuous Query, but it doesn't seem to have any effect. My code is like:
private void configOrderListener(Ignite ignite) {
IgniteCache cache =
ignite.cache(StoreHelper.getCacheName(OrderStore.class));
