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/06/28 09:32:00 UTC

[jira] [Created] (IGNITE-19865) Improve propagation of trace identifier in exception classes

Vyacheslav Koptilin created IGNITE-19865:
--------------------------------------------

             Summary: Improve propagation of trace identifier in exception classes
                 Key: IGNITE-19865
                 URL: https://issues.apache.org/jira/browse/IGNITE-19865
             Project: Ignite
          Issue Type: Improvement
            Reporter: Vyacheslav Koptilin
            Assignee: Vyacheslav Koptilin


For now, the proper way of propagating a trace identifier from one exception to another one requires writing boilerplate code or using the `withCauseAndCode` method. This approach is not convenient, it should be possible to write a simple code as follows:

{code:java}
    try {
        ...
    } catch (IgniteSpecificExceptionA | IgniteSpecificExceptionB e) {
       throw new ComponentException("Failed to exceute..", e); // trace id should be properly propagated to ComponentException.
{code}




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