[jira] [Updated] (IGNITE-17312) Thin 3.0: Unified exception handling
[ https://issues.apache.org/jira/browse/IGNITE-17312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn updated IGNITE-17312: 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. # 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.) was: 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 (when enabled in server-side ClientConnectorConfig. Disabled by default.) > 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 > > > 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)
[jira] [Updated] (IGNITE-17312) Thin 3.0: Unified exception handling
[ https://issues.apache.org/jira/browse/IGNITE-17312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn updated IGNITE-17312: 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. # 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 (when enabled in server-side ClientConnectorConfig. Disabled by default.) was: 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. > 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 > > > 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 (when enabled in server-side > ClientConnectorConfig. Disabled by default.) -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-17312) Thin 3.0: Unified exception handling
[ https://issues.apache.org/jira/browse/IGNITE-17312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn updated IGNITE-17312: 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. was:TODO > 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 > > > 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. -- This message was sent by Atlassian Jira (v8.20.10#820010)
