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 2017/02/17 10:58:41 UTC

[jira] [Commented] (ATLAS-1566) Use Jackson ObjectMapper for serialization and deserailization

    [ https://issues.apache.org/jira/browse/ATLAS-1566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15871666#comment-15871666 ] 

David Radley commented on ATLAS-1566:
-------------------------------------

I think this makes sense. 

Just be aware for types that have attributes pointing to themselves like parent child relationships or other loops, we use object_ids.  It looks like Jackson does have annotations to help avoid this sort of thing with: @JsonManagedReference and @JsonBackReference; we do not need to use these as we use the object_ids. I suggest including unit tests to test these loop scenarios (1 to 1 and 1 to many; to own type and other types).      

> Use Jackson ObjectMapper for serialization and deserailization
> --------------------------------------------------------------
>
>                 Key: ATLAS-1566
>                 URL: https://issues.apache.org/jira/browse/ATLAS-1566
>             Project: Atlas
>          Issue Type: Improvement
>            Reporter: Vimal Sharma
>            Assignee: Vimal Sharma
>             Fix For: 0.8-incubating
>
>         Attachments: ATLAS-1566.1.patch
>
>
> Currently, GSON is used for serialization and deserialization of AtlasType POJOs at REST layer. ObjectMapper from Jackson library is used at other places in the Atlas code. Use ObjectMapper in AtlasType to make the serialization/deserialization consistent across Atlas code.



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