t; By executing these two test codes in the description, it is easy to
>> reproduce the problem.
>>
>>
>>
>> What should I do next? Continuously following this Jira?
>>
>>
>>
>>
>>
>> 发件人: Jeremy McMillan
>> 发送时间: 2023年5月
these two test codes in the description, it is easy to
> reproduce the problem.
>
>
>
> What should I do next? Continuously following this Jira?
>
>
>
>
>
> *发件人: *Jeremy McMillan
> *发送时间: *2023年5月24日 23:24
> *收件人: *user@ignite.apache.org
> *主题: *Re: Ignite t
5月24日 23:24
收件人: user@ignite.apache.org
主题: Re: Ignite thin client continuous query listener cannot listen to all events
Thanks for bringing this up!
https://ignite.apache.org/docs/latest/key-value-api/continuous-queries#events-delivery-guarantees
This sounds like you may have found a bug
Thanks for bringing this up!
https://ignite.apache.org/docs/latest/key-value-api/continuous-queries#events-delivery-guarantees
This sounds like you may have found a bug, but the details you've provided
are not sufficient to help others recreate and observe it for themselves,
and this effort
Hi,
I have a question while using ignite 2.15.0
Problem scenario:
Start the Ignite server of one node, start one thin client and create a
continuous query listener, and then use 50 threads to add 500 data to the cache
concurrently.
Problem phenomenon:
Through the information printed on the