[
https://issues.apache.org/jira/browse/IGNITE-19536?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vyacheslav Koptilin updated IGNITE-19536:
-----------------------------------------
Description:
It seems useful to introduce a marker/flag in order to differentiate
recoverable and non-recoverable errors. This approach should simplify exception
handling on the client side.
Something as follows:
{code:java}
try {
igniteCompute.execute();
}
catch (IgniteComputeException error) {
if (error is recoverable) {
// Put retry logic here.
}
}
{code}
was:
It seems useful to introduce a marker/flag in order to differentiate
recoverable and non-recoverable errors. This approach should simplify exception
handling on the client side.
Something as follows:
{code:java}
try {
igniteCompute.execute();
}
catch (IgniteComputeException error) {
if (error is recoverable) {
// Put retry logic here.
}
}
{code}
> Introduce a "recoverable" flag to differentiate recoverable and
> non-recoverable exceptions
> ------------------------------------------------------------------------------------------
>
> Key: IGNITE-19536
> URL: https://issues.apache.org/jira/browse/IGNITE-19536
> Project: Ignite
> Issue Type: Improvement
> Reporter: Vyacheslav Koptilin
> Assignee: Vyacheslav Koptilin
> Priority: Major
> Labels: iep-84, ignite-3
> Fix For: 3.0.0-beta2
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> It seems useful to introduce a marker/flag in order to differentiate
> recoverable and non-recoverable errors. This approach should simplify
> exception handling on the client side.
> Something as follows:
> {code:java}
> try {
> igniteCompute.execute();
> }
> catch (IgniteComputeException error) {
> if (error is recoverable) {
> // Put retry logic here.
> }
> }
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
