[
https://issues.apache.org/jira/browse/ATLAS-520?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16025238#comment-16025238
]
Mandy Chessell commented on ATLAS-520:
--------------------------------------
The proposed data model for versioned metadata objects is show on wiki page
https://cwiki.apache.org/confluence/display/ATLAS/Area+0+-+Extensions+to+the+base+model
> Temporal / Versioning support for types, traits, entites ....
> -------------------------------------------------------------
>
> Key: ATLAS-520
> URL: https://issues.apache.org/jira/browse/ATLAS-520
> Project: Atlas
> Issue Type: Wish
> Affects Versions: trunk
> Reporter: Nigel Jones
> Labels: VirtualDataConnector
>
> With Atlas storing metadata & lineage data , from a governance perspective we
> would like to ask questons such as
> - what different data sources were used to produce this report last year
> compared to this year?
> - how was this salary column in the employee table classified on 6 Apr 2015?
> These queries are needed to support audit, and to aid in process improvement
> + root cause analysis
> To do so we need temporal support in atlas. A query should be able to
> indicate the point in time that it applies to. This means keeping track of
> times, versions within atlas. Potentially this means not just the nodes in
> the graph, but the edges too, however this can mean an ever increasing graph
> which can get out of control.
> opening up this JIRA to enable an evaluation/ discussion of what we might be
> able to do
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
