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

Madhan Neethiraj resolved ATLAS-4759.
-------------------------------------
    Fix Version/s: 3.0.0
                   2.4.0
         Assignee: Maxim Martynov
       Resolution: Fixed

[~dolfinus]  - thank you for the fix. The patch is now merged in following 
branches:

 
{noformat}
commit b7849aeb78856f2f8e205c5e784cee84409cbc72 (HEAD -> master, origin/master, 
origin/HEAD)
Author: Maxim Martynov <martinov_m...@mail.ru>
Date:   Mon Jun 5 12:33:35 2023 -0700

    ATLAS-4759: Python client - do not suppress HTTP 503 (SERVICE_UNAVAILABLE)

    Signed-off-by: Madhan Neethiraj <mad...@apache.org>
{noformat}
 

 
{noformat}
commit b1d9450761de70adf9b3ecd35b5f62dc31d70489 (HEAD -> branch-2.0, 
origin/branch-2.0)
Author: Maxim Martynov <martinov_m...@mail.ru>
Date:   Mon Jun 5 12:33:35 2023 -0700

    ATLAS-4759: Python client - do not suppress HTTP 503 (SERVICE_UNAVAILABLE)

    Signed-off-by: Madhan Neethiraj <mad...@apache.org>
    (cherry picked from commit b7849aeb78856f2f8e205c5e784cee84409cbc72)
{noformat}

> Atlas Python client suppresses 503 error
> ----------------------------------------
>
>                 Key: ATLAS-4759
>                 URL: https://issues.apache.org/jira/browse/ATLAS-4759
>             Project: Atlas
>          Issue Type: Bug
>          Components: atlas-intg
>    Affects Versions: 2.1.0
>            Reporter: Maxim Martynov
>            Assignee: Maxim Martynov
>            Priority: Major
>             Fix For: 3.0.0, 2.4.0
>
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> Currently if Python client for Apache Atlas gets HTTP 503 error code, it 
> always returns {{None}}:
> https://github.com/apache/atlas/blob/b19fba2ad96e3007af79d646ba17b6bd783d9156/intg/src/main/python/apache_atlas/client/base_client.py#L113-L116
> So if someone writes data to Atlas (e.g. update entity properties, save 
> lineage info), there is no distinction if {{None}} is returned because it is 
> supposed to do (e.g. 204 No content) or Atlas is not available.
> It is recommended to raise exception here.



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

Reply via email to