[jira] [Updated] (IGNITE-17193) Map IgniteException to problem json

["Vyacheslav Koptilin (Jira)" <ji...@apache.org>]

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

Vyacheslav Koptilin updated IGNITE-17193:
-----------------------------------------
    Issue Type: Improvement  (was: Task)

> Map IgniteException to problem json
> -----------------------------------
>
>                 Key: IGNITE-17193
>                 URL: https://issues.apache.org/jira/browse/IGNITE-17193
>             Project: Ignite
>          Issue Type: Improvement
>            Reporter: Aleksandr
>            Assignee: Aleksandr
>            Priority: Major
>              Labels: ignite-3
>             Fix For: 3.0.0-alpha6
>
>          Time Spent: 50m
>  Remaining Estimate: 0h
>
> According to https://www.rfc-editor.org/rfc/rfc7807.html HTTP API has to return application/problem+json if an error happens. 
> https://cwiki.apache.org/confluence/display/IGNITE/IEP-84%3A+Error+handling describes how Ignite 3 throws exceptions. 
> The aim of this ticket is to map IgniteException to application/problem+json. Note, that there is no implementation of IEP-84. So, leave TODOs with Jira tickets where it is needed.
> Mapping strategy:
> “title”: a short, human-readable summary of the problem type
> “status”: HTTP status code 
> “code”: error code
> “type”: URI to the error documentation (optional)
> “detail”: a human-readable explanation of the problem (optional)
> “invalid-params”: list of parameters that did not pass the validation (optional)
> “node”: Ignite 3 node name (optional)
> “trace-id”: unique identifier that will help to trace the error in the log (optional).



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