atlas-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Madhan Neethiraj (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (ATLAS-1747) Difference in result of POSTing Structs to V1 APIs and V2 APIs
Date Wed, 17 May 2017 16:54:04 GMT

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

Madhan Neethiraj updated ATLAS-1747:
------------------------------------
       Affects Version/s:     (was: 0.9-incubating)
    Request participants:   (was: )
           Fix Version/s: 0.8.1-incubating

> Difference in result of POSTing Structs to V1 APIs and V2 APIs
> --------------------------------------------------------------
>
>                 Key: ATLAS-1747
>                 URL: https://issues.apache.org/jira/browse/ATLAS-1747
>             Project: Atlas
>          Issue Type: Bug
>          Components:  atlas-core
>    Affects Versions: 0.8-incubating
>            Reporter: Sharmadha Sainath
>            Assignee: Apoorv Naik
>            Priority: Critical
>             Fix For: 0.9-incubating, 0.8.1-incubating
>
>         Attachments: struct_V1_API_400_Bad_Req.txt, struct_V2_API_200_OK.txt
>
>
> Created a struct without attribute definitions.
> 1. POSTing it to V1 APIs threw 400 Bad Request with exception 
> {code}
> Caused by: java.lang.IllegalArgumentException: Collection Attribute definitions is empty
> {code}
> 2. POSTing it to V2 APIs throws the above exception but struct is created successfully.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message