[
https://issues.apache.org/jira/browse/IGNITE-17312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17571479#comment-17571479
]
Pavel Tupitsyn commented on IGNITE-17312:
-----------------------------------------
Merged to main: d4cd82d22e7743c6b5f00b3ef342648752319450
> Thin 3.0: Unified exception handling
> ------------------------------------
>
> Key: IGNITE-17312
> URL: https://issues.apache.org/jira/browse/IGNITE-17312
> Project: Ignite
> Issue Type: Improvement
> Components: thin client
> Reporter: Pavel Tupitsyn
> Assignee: Pavel Tupitsyn
> Priority: Major
> Labels: ignite-3
> Fix For: 3.0.0-alpha6
>
> Time Spent: 1h 40m
> Remaining Estimate: 0h
>
> Java thin client uses the same public API interfaces as the server side.
> Those user-facing APIs should behave in the same way on the server and client
> sides, including exceptions that may be thrown.
> # Remove *IgniteClientException*.
> # Keep *IgniteClientConnectionException* and other client-specific types.
> Inherit them from *IgniteException*.
> # When sending exception details from server to client, include the following:
> ## Code (group + error, see IgniteException.code)
> ## TraceId
> ## Message
> ## Fully-qualified class name
> ## OPTIONALLY: stack trace (Sensitive info. Send only when enabled in
> server-side ClientConnectorConfig. Disabled by default.)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
