atlas-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Radley (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ATLAS-1410) V2 Glossary API
Date Mon, 20 Mar 2017 12:21:41 GMT

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

David Radley commented on ATLAS-1410:
-------------------------------------

Responding to [~jonesn]
6- Ok so a term belongs in a glossary, but can be categorized by one in another . I understand
this from an object perspective but trying to think of an example as to why that is needed?
I guess I'm not clear on the meaning of having multiple glossaries that are interlinked <<
David this allows us to separate terms into subject areas. It also allows duplicate term names
to occur by putting them in different glossaries; something Stefhan is keen on. Also glossaries
are the owning entity for terms, so there is no need for a single owning category. >>
 

8- Are you saying that additional attribute values can be stored with the classification object?
I'm thinking here of the example tag based policies covered at section 8.2 of https://cwiki.apache.org/confluence/display/RANGER/Tag+Based+Policies
where "EXPIRES_ON" is referred to << David the classification type would be subclassed
and new attributes added>> 


> V2 Glossary API
> ---------------
>
>                 Key: ATLAS-1410
>                 URL: https://issues.apache.org/jira/browse/ATLAS-1410
>             Project: Atlas
>          Issue Type: Improvement
>            Reporter: David Radley
>            Assignee: David Radley
>         Attachments: Atlas Glossary V2 proposal v1.0.pdf, Atlas Glossary V2 proposal
v1.1.pdf
>
>
> The BaseResourceDefinition uses the AttributeDefintion class from typesystem. There are
newer more funcitonal versions of this capability in the atlas-intg project. This Jira is
changing over the glossary implementation to the newer entity / type classes.  
> Instread of the instanceProperties and collectionProperties in the BaseResourceDefintions
we should use something in this sort of style :  
> "
>  AtlasEntityDef deptTypeDef =
>                 AtlasTypeUtil.createClassTypeDef(DEPARTMENT_TYPE, "Department"+_description,
ImmutableSet.<String>of(),
>                         AtlasTypeUtil.createRequiredAttrDef("name", "string"),
>                         new AtlasAttributeDef("employees", String.format("array<%s>",
"Person"), true,
>                                 AtlasAttributeDef.Cardinality.SINGLE, 0, 1, false, false,
>                                 Collections.<AtlasStructDef.AtlasConstraintDef>emptyList()));
>         AtlasEntityDef personTypeDef = AtlasTypeUtil.createClassTypeDef("Person", "Person"+_description,
ImmutableSet.<String>of(),
>                 AtlasTypeUtil.createRequiredAttrDef("name", "string"),
>                 AtlasTypeUtil.createOptionalAttrDef("address", "Address"),
>                 AtlasTypeUtil.createOptionalAttrDef("birthday", "date"),
>                 AtlasTypeUtil.createOptionalAttrDef("hasPets", "boolean"),
>                 AtlasTypeUtil.createOptionalAttrDef("numberOfCars", "byte"),
>                 AtlasTypeUtil.createOptionalAttrDef("houseNumber", "short"),
>                 AtlasTypeUtil.createOptionalAttrDef("carMileage", "int"),
>                 AtlasTypeUtil.createOptionalAttrDef("age", "float"),
> "
> For the parent child relationships with glossary categories and terms we should be able
to have the type system manage edge deletion. As part of this, we will need to investigate
whether we could get rid of the disconnect and connect methods added in ATLAS-1186 
>  



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

Mime
View raw message