[
https://issues.apache.org/jira/browse/ATLAS-1410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15928458#comment-15928458
]
Nigel Jones commented on ATLAS-1410:
------------------------------------
Thanks David
* 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
* ok to defer internationalization.. though as well as display names
relationships like homonyms could be affected since they are sound/dialect as
well as country/language specific (this is somewhat peripheral for most I agree)
* 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
* ranger tagsync - yes I think we have what's needed. See the referenced ATLAS
Jira I opened on a new interface to support the new glossary (including
flattening the structure down to simple tags). An example of the JSON that ends
up being sent to the ranger server (after extracting from atlas... and we'll
use a new API for this... and then going through tagsync) is
https://github.com/apache/ranger/blob/master/tagsync/src/main/resources/etc/ranger/data/tags.json
> 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)
