[IGNITE-17312] Thin 3.0: Unified exception handling

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 3.0.0-beta1
• Component/s: thin client
• Labels: ignite-3
• Ignite Flags: Docs Required, Release Notes Required
• Assignee: Pavel Tupitsyn
• Reporter: Pavel Tupitsyn
• Reviewer: Igor Sapego
• Created: 06/Jul/22 09:59
• Updated: 13/Oct/22 12:01
• Resolved: 26/Jul/22 14:57

Description

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.

1. Remove IgniteClientException.
2. Keep IgniteClientConnectionException and other client-specific types. Inherit them from IgniteException.
3. When sending exception details from server to client, include the following:
   1. Code (group + error, see IgniteException.code)
   2. TraceId
   3. Message
   4. Fully-qualified class name
   5. OPTIONALLY: stack trace (Sensitive info. Send only when enabled in server-side ClientConnectorConfig. Disabled by default.)

Issue Links

• blocks: IGNITE-17135 SQL API: Exceptions are different on server and client
• blocks: IGNITE-17314 .NET: Thin 3.0: Unified exception handling
• is related to: IGNITE-14931 Define common error scopes and prefix
• links to: GitHub Pull Request #949
• links to: IGNITE-17312 Java thin: Implement unified exception handling by ptupitsyn · Pull Request #949 · apache/ignite-3