You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Vyacheslav Koptilin (Jira)" <ji...@apache.org> on 2023/05/22 15:56:00 UTC
[jira] [Updated] (IGNITE-19535) Removing the constraint that all internal exceptions should implement the mandatory constructor Exception(UUID, int, String, Throwable)
[ https://issues.apache.org/jira/browse/IGNITE-19535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Vyacheslav Koptilin updated IGNITE-19535:
-----------------------------------------
Labels: iep-84 ignite-3 (was: ignite-3)
> Removing the constraint that all internal exceptions should implement the mandatory constructor Exception(UUID, int, String, Throwable)
> ---------------------------------------------------------------------------------------------------------------------------------------
>
> Key: IGNITE-19535
> URL: https://issues.apache.org/jira/browse/IGNITE-19535
> Project: Ignite
> Issue Type: Improvement
> Reporter: Vyacheslav Koptilin
> Assignee: Vyacheslav Koptilin
> Priority: Major
> Labels: iep-84, ignite-3
> Fix For: 3.0.0-beta2
>
>
> For now, it is required that all internal exceptions should have a constructor with the following parameters:
> {code:java}
> InternalException(UUID traceId, int code, String message, Throwable cause)
> {code}
>
> This requirement looks a bit restrictive. Need to find a way to improve implementation in order to avoid this.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)