Hello!

Futures will accept a timeout value in their get() method and will only
wait for that timeout, you do not have to count milliseconds by hand.

Regards,
-- 
Ilya Kasnacheev


вт, 22 сент. 2020 г. в 15:31, Kamlesh Joshi <[email protected]>:

> Thanks ilya. Does that mean, we have to specifically maintain a time
> counter and act accordingly on it?
>
>
>
> I was hoping, if there is any API where we could just pass timeout value
> as well, as a parameter and Ignite would handle internally.
>
>
>
> *Thanks and Regards,*
>
> *Kamlesh Joshi*
>
>
>
> *From:* Ilya Kasnacheev <[email protected]>
> *Sent:* 22 September 2020 17:10
> *To:* [email protected]
> *Subject:* [External]Re: how to achieve timeout for get/put/remove
> operations
>
>
>
> The e-mail below is from an external source. Please do not open
> attachments or click links from an unknown or suspicious origin.
>
> Hello!
>
>
>
> You can use e.g. putAsync() and then wait on the future for the specified
> time only. If it did not complete, take your actions.
>
>
>
> Regards,
>
> --
>
> Ilya Kasnacheev
>
>
>
>
>
> вт, 22 сент. 2020 г. в 14:27, Kamlesh Joshi <[email protected]>:
>
> Hi Igniters,
>
>
>
> How to achieve/get timeout error for particular operation
> (get/put/remove), if it crosses certain timeout value then I can take
> certain action based on that. Is there any Ignite API readily available for
> this?
>
>
>
> Any pointers would be helpful !
>
>
>
>
>
> *Thanks and Regards,*
>
> *Kamlesh Joshi*
>
>
>
>
> "*Confidentiality Warning*: This message and any attachments are intended
> only for the use of the intended recipient(s), are confidential and may be
> privileged. If you are not the intended recipient, you are hereby notified
> that any review, re-transmission, conversion to hard copy, copying,
> circulation or other use of this message and any attachments is strictly
> prohibited. If you are not the intended recipient, please notify the sender
> immediately by return email and delete this message and any attachments
> from your system.
>
> *Virus Warning:* Although the company has taken reasonable precautions to
> ensure no viruses are present in this email. The company cannot accept
> responsibility for any loss or damage arising from the use of this email or
> attachment."
>
>
> "*Confidentiality Warning*: This message and any attachments are intended
> only for the use of the intended recipient(s), are confidential and may be
> privileged. If you are not the intended recipient, you are hereby notified
> that any review, re-transmission, conversion to hard copy, copying,
> circulation or other use of this message and any attachments is strictly
> prohibited. If you are not the intended recipient, please notify the sender
> immediately by return email and delete this message and any attachments
> from your system.
>
> *Virus Warning:* Although the company has taken reasonable precautions to
> ensure no viruses are present in this email. The company cannot accept
> responsibility for any loss or damage arising from the use of this email or
> attachment."
>

Reply via email to