[
https://issues.apache.org/jira/browse/ATLAS-559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15189110#comment-15189110
]
Hemanth Yamijala commented on ATLAS-559:
----------------------------------------
ATLAS-543 has the same spirit, but is focussed on the IDs primarily - hence
might be a more focussed fix that can come in faster.
> 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
>
> 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)
