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

Posted to dev@atlas.apache.org by "Neeru Gupta (JIRA)" <ji...@apache.org> on 2016/06/06 14:58:21 UTC

[jira] [Assigned] (ATLAS-559) Atlas should allow JSONs to be submitted that don't have optional attributes.

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

Neeru Gupta reassigned ATLAS-559:
---------------------------------

    Assignee:     (was: Neeru Gupta)

> Atlas should allow JSONs to be submitted that don't have optional attributes.
> -----------------------------------------------------------------------------
>
>                 Key: ATLAS-559
>                 URL: https://issues.apache.org/jira/browse/ATLAS-559
>             Project: Atlas
>          Issue Type: Bug
>            Reporter: Hemanth Yamijala
>             Fix For: 0.7-incubating
>
>
> Currently, attributes which are in principle optional should still be submitted using a null value if one is using the REST API directly. The Java client libraries handle this case for the user, but there are non Java folks using Atlas as well. For them, any optional addition to the types implies they will need to change their code which is super inconvenient. Hence, handling optional attributes is required.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)