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-19539) Introduce exception handler to prevent leaking internal exceptions to the end user

     [ https://issues.apache.org/jira/browse/IGNITE-19539?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Vyacheslav Koptilin updated IGNITE-19539:
-----------------------------------------
    Labels: iep-84 ignite-3  (was: ignite-3)

> Introduce exception handler to prevent leaking internal exceptions to the end user
> ----------------------------------------------------------------------------------
>
>                 Key: IGNITE-19539
>                 URL: https://issues.apache.org/jira/browse/IGNITE-19539
>             Project: Ignite
>          Issue Type: Bug
>            Reporter: Vyacheslav Koptilin
>            Assignee: Vyacheslav Koptilin
>            Priority: Major
>              Labels: iep-84, ignite-3
>             Fix For: 3.0.0-beta2
>
>
> It seems reasonable to introduce some kind of mapper/handler of internal exceptions in order to prevent leaking internal exceptions to the end user.
> All public methods/interfaces should only throw IgniteException/IgniteCheckedException instances and their subclasses.
> All internal exceptions should be mapped to IgniteException with the INTERNAL_ERR error code and be considered as a bug.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)