atlas-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sarath Subramanian (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (ATLAS-2078) Updating a type using v1 API doesn't route to createUpdateTypesDef in v2 API
Date Tue, 22 Aug 2017 22:09:00 GMT

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

Sarath Subramanian updated ATLAS-2078:
--------------------------------------
    Attachment: ATLAS-2078.1.patch

> Updating a type using v1 API doesn't route to createUpdateTypesDef in v2 API
> ----------------------------------------------------------------------------
>
>                 Key: ATLAS-2078
>                 URL: https://issues.apache.org/jira/browse/ATLAS-2078
>             Project: Atlas
>          Issue Type: Bug
>          Components:  atlas-core
>    Affects Versions: 0.9-incubating, 0.8.1-incubating
>            Reporter: Sarath Subramanian
>            Assignee: Sarath Subramanian
>            Priority: Critical
>             Fix For: 0.9-incubating, 0.8.1-incubating
>
>         Attachments: ATLAS-2078.1.patch
>
>
> When updating types using v1 API, if type doesn't exist we create missing types. Currently
this API maps to v2 API's update method and doesn't create missing types.
>  



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message