[
https://issues.apache.org/jira/browse/ATLAS-1245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15742654#comment-15742654
]
Apoorv Naik commented on ATLAS-1245:
------------------------------------
Hey David,
There are new v2 APIs in place in which all the types and entities have GUIDs.
Can you check if that suffices ?
> More objects should have a unique guid
> --------------------------------------
>
> Key: ATLAS-1245
> URL: https://issues.apache.org/jira/browse/ATLAS-1245
> Project: Atlas
> Issue Type: Improvement
> Environment:
> Reporter: David Radley
> Assignee: David Radley
>
> Currently only some Atlas objects have guids. The entity REST API exposes
> guids as the unique identifiers by which entities can be found.
> Some objects like taxonomy have a guid internally but externally it is
> referenced by name. My feeling is that an object can have a unique guid and a
> unique name.
> Some objects like trait and trait instance do not have guids at all. So their
> management is tied to their name.
> Having a unique identifier for all objects allows for common ways for them to
> be managed, it also means that renames do not change the object identity.
> We have system level attributes already. In a similar way I suggest we add in
> guids to all objects.
> Also at the graph level if every vertex has a guid property - which is
> indexed, Gremlin queries are simpler (possibly more perfomant), and edges can
> be created in a standard way by supplying the in and out guids.
> I suggest types, traits and trait types gain a guid.
> I can see that some artifacts like comments may not need an exposed guid.
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
