atlas-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Madhan Neethiraj (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ATLAS-1768) Create common types for Open Metadata
Date Fri, 09 Jun 2017 03:37:19 GMT

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

Madhan Neethiraj commented on ATLAS-1768:
-----------------------------------------

bq. Is the plan that a query for historic state (e.g. what was the state on 4th January 2017)
can be created from rolling forward through the JSON records?
Historic state stored in audit log contains all attribute values; however I think it doesn't
include details like associated classifications/classification attributes. Perhaps we should
look to enhance what gets stored in audit record.

> Create common types for Open Metadata
> -------------------------------------
>
>                 Key: ATLAS-1768
>                 URL: https://issues.apache.org/jira/browse/ATLAS-1768
>             Project: Atlas
>          Issue Type: New Feature
>          Components:  atlas-core
>    Affects Versions: 0.9-incubating
>            Reporter: Mandy Chessell
>            Assignee: Mandy Chessell
>              Labels: OpenMetadata
>
> This JIRA describes a proposal for standard types for open metadata entities and relationships.
 For example, glossaries, database definitions, rules, policies, ...
> The value of having standard definitions for metadata is to enable type safe APIs and
business level UIs plus be able to exchange metadata between different instances of metadata
repositories.
> The implementation of these common types is divided into 8 areas:
> * Area 0 - for extensions to Apache Atlas's base model
> * Area 1 - for definitions of the data-related assets we are governing and using
> * Area 2 - for a glossary of meanings and semantic relationships
> * Area 3 - for information about asset use, crowd-sourced definitions and collaboration
around the data-related assets
> * Area 4 - for governance such as policies, rules and classifications
> * Area 5 - for reference models and reference data
> * Area 6 - for metadata discovery processes (see https://issues.apache.org/jira/browse/ATLAS-1748)
> * Area 7 - for lineage
> Adaptation and flexibility are key in metadata environments so these common definitions
must be extensible - and we still need to support the ad hoc definition of new types in Atlas.
> Apache Atlas supports meta-types that are used in the definition of new types.  These
are currently enumeration, struct, classification and entity.  JIRA https://issues.apache.org/jira/browse/ATLAS-1690
adds relationships to this list.  The open metadata models make use of all of these meta-types.
 These are represented by sterotypes on the classes of the open metadata definitions.
> The Atlas wiki has the models as a set of linked pages which are probably the easiest
way to view the models.
> Start here: https://cwiki.apache.org/confluence/display/ATLAS/Building+out+the+Apache+Atlas+Typesystem



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

Mime
View raw message