You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@atlas.apache.org by "Ashutosh Mestry (Jira)" <ji...@apache.org> on 2019/11/04 20:21:00 UTC

[jira] [Assigned] (ATLAS-3506) ALTAS import fails when AtlasClient is used but succeeds when curl is using in Knox trusted proxy setup

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

Ashutosh Mestry reassigned ATLAS-3506:
--------------------------------------

    Assignee: Ashutosh Mestry

> ALTAS import fails when AtlasClient is used but succeeds when curl is using in Knox trusted proxy setup
> -------------------------------------------------------------------------------------------------------
>
>                 Key: ATLAS-3506
>                 URL: https://issues.apache.org/jira/browse/ATLAS-3506
>             Project: Atlas
>          Issue Type: Bug
>          Components:  atlas-core
>    Affects Versions: 3.0.0
>            Reporter: Mukund Thakur
>            Assignee: Ashutosh Mestry
>            Priority: Critical
>              Labels: dlm-engine
>
> Data life cycle manager uses Atlas client to call import for hive databases. We have a knox based trusted proxy setup when this call fails with 500 Internal Sever Error. But the same exact call succeeds when curl is used in place of atlas java client. 
> I debugged this and found that Atlas client doesn't set  "Expect", "100-continue" header and curl automatically sets this. I have a patch where i added this header in the atlas client java code and post that it works fine. 
> Let me know if anybody has any specific questions. 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)