atlas-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nigel Jones (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ATLAS-2251) Remove/replace use of TypeSystem with AtlasTypeRegistry
Date Wed, 15 Nov 2017 00:19:00 GMT

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

Nigel Jones commented on ATLAS-2251:
------------------------------------

The patch may need rebasing - that error I posted now seems fixed. Getting a Hive Hook IT
error now but I think that is a seperate issue so once rebased I think patch is good....

> Remove/replace use of TypeSystem with AtlasTypeRegistry
> -------------------------------------------------------
>
>                 Key: ATLAS-2251
>                 URL: https://issues.apache.org/jira/browse/ATLAS-2251
>             Project: Atlas
>          Issue Type: Task
>          Components:  atlas-core
>    Affects Versions: 1.0.0
>            Reporter: Madhan Neethiraj
>            Assignee: Madhan Neethiraj
>            Priority: Critical
>             Fix For: 1.0.0
>
>         Attachments: ATLAS-2251-1.patch, ATLAS-2251-3.patch, ATLAS-2251-4.patch
>
>
> With introduction of V2 APIs in 0.8 release, Atlas core type-system implementation moved
to use AtlasTypeRegistry (which uses data-structures introduced in V2 APIs). However, earlier
version equivalent, TypeSystem (which uses V1 data-structures), is still being referenced
in few places, like:
>  - V1 REST APIs, to covert between V1 and V2 data-structures
>  - notification processing, which uses V1 data-structures
>  - DSL query implementation
>  - AtlasClient API
>  - unit tests
> Having to support legacy TypeSystem causes run time overhead in duplicate caching of
type-information - in AtlasTypeRegistry and TypeSystem. Removing TypeSystem implementation
will help eliminate this overhead and also improve maintainability of Atlas sources.
> This JIRA is to track removal of TypeSystem implementation and its references; where
necessary, references should be updated to use AtlasTypeRegistry equivalent.
> - it is very critical to continue to support V1 REST APIs and processing of current V1
notifications 
> - existing unit tests that use V1 data-structures will be removed and will be replaced
with equivalents that use V2 data-structures
> - AtlasClient in new release will only support V2 data-structures; however, older version
AtlasClient will continue to work with new version of Atlas server



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

Mime
View raw message