[
https://issues.apache.org/jira/browse/ATLAS-1747?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15981023#comment-15981023
]
Sharmadha Sainath commented on ATLAS-1747:
------------------------------------------
After POSTing faulty definition with no attributeDefs for a struct to V2 APIs,
type registration is not happening properly.
1.Created a correct type of category entity after Atlas accepted faulty
definition for struct.
2.The type got created successfully.
3.But while searching the type , Atlas throws 500 Internal server error .
Unable to create entity for the type also.
Whenever new type is registered , exception attached in
struct_V2_API_200_OK.txt is thrown.
Changing priority to critical.
> 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, 0.9-incubating
> Reporter: Sharmadha Sainath
> 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)
