Carlos Angarita created ATLAS-2278:
--------------------------------------

             Summary: AtlasClientV2 not able to load type registry on windows
                 Key: ATLAS-2278
                 URL: https://issues.apache.org/jira/browse/ATLAS-2278
             Project: Atlas
          Issue Type: Bug
    Affects Versions: 1.0.0
         Environment: Windows
            Reporter: Carlos Angarita


In windows, the Atlas client V2 tries to access an http url using the wrong 
format (backslashes instead of forward slashes)
I paste below the logger information from the client, and server.

Client information
{code:java}
2017-11-24 10:59:36.400  INFO 468 --- [  restartedMain] o.a.a.AtlasBaseClient   
                 : ------------------------------------------------------
2017-11-24 10:59:36.400  INFO 468 --- [  restartedMain] o.a.a.AtlasBaseClient   
                 : Call         : GET api\atlas\v2\types\typedefs
2017-11-24 10:59:36.402  INFO 468 --- [  restartedMain] o.a.a.AtlasBaseClient   
                 : Content-type : application/json; charset=UTF-8
2017-11-24 10:59:36.402  INFO 468 --- [  restartedMain] o.a.a.AtlasBaseClient   
                 : Accept       : application/json
2017-11-24 10:59:37.181 ERROR 468 --- [  restartedMain] c.c.p.m.t.Registry      
                 : Unable to load type registry!

org.apache.atlas.AtlasServiceException: Metadata service API 
org.apache.atlas.AtlasClientV2$API_V2@7400ad83 failed with status 404 (Not 
Found) Response Body (<!doctype html>
{code}

Atlas Server audit.log: (the request was parsed to escaped backslashes, then 
404 error was returned)
{code:java}
2017-11-24 20:33:19,855  Audit: admin/10.0.75.1-10.0.75.1 performed request GET 
http://10.0.75.2:21000/api%5Catlas%5Cv2%5Ctypes%5Ctypedefs (10.0.75.2) at time 
2017-11-24T20:33Z
{code}

AtlasBaseClient normalizes the url paths so there is where the url problem 
seems to come from:
https://github.com/apache/atlas/blob/master/client/common/src/main/java/org/apache/atlas/AtlasBaseClient.java#L616




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Reply via email to