You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@atlas.apache.org by "David Radley (JIRA)" <ji...@apache.org> on 2018/01/02 11:00:00 UTC
[jira] [Commented] (ATLAS-2327) Regression : Creating entity using
V1 APIs with invalid values for attribute types succeeds
[ https://issues.apache.org/jira/browse/ATLAS-2327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16307880#comment-16307880 ]
David Radley commented on ATLAS-2327:
-------------------------------------
I think the emphasis should be that we fix and enhance the V2 APIs; these are more functionally rich than the older V1 APIs.
Note that the Jackson json parsing Atlas does, intentionally ignores json keys it does not recognise. If this is a mis spelt optional field, you may get behavour you do not expect..
> Regression : Creating entity using V1 APIs with invalid values for attribute types succeeds
> -------------------------------------------------------------------------------------------
>
> Key: ATLAS-2327
> URL: https://issues.apache.org/jira/browse/ATLAS-2327
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
> Reporter: Sharmadha Sainath
>
> Creating an entity with invalid values using V1 APIs succeeds with 201. Expected is 400 Bad Request.
> This doesn't happen with V2 APIs.
> Example :
> 1.Create type by posting JSON to /api/atlas/types
> 2.Create entity with random string value for float attribute by posting JSON to /api/atlas/entities
> 3. Request succeeds with 201.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)