[
https://issues.apache.org/jira/browse/ATLAS-1410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15932746#comment-15932746
]
David Radley commented on ATLAS-1410:
-------------------------------------
Thanks you very much for the feedback [~Stefhan]. some responses
Page 5:
Use case 1: Changed as discussed
Use case 2 and Page 6:
<<David We were thinking that the glossary would have been the scoping here- do
you think this is too course grain? I wonder if you have an example about the
styles of management that might clash and that might show the need for a parent
category>>
Page 7: <<David Changed as discussed>>
Unclear why there is a need to have different term types. <<David removed the
concept and attribute terms and replaced with semantic term as discussed>>
Page 8 "A Classification points to one entity and can have many associated
term." I don't think i fully understand this statement. It would be wiser to
have the classification point to one or more terms and that the term will point
to one or more entities. To be further discussed. <<David lets discuss further.
The idea is that the classification will be on the relationship. So the
classification will cease to be active when the term is deleted , the entity is
the deleted or they become dissociated. Currently the classification points to
only the entity; we are augmenting this design by adding the terms to the
classification. I think it is useful that the classification is on the
relationship at runtime so that we can ad attributes to this classification
that are entity or term specific. Does this help? Am I missing something? >>
Also it should be possible to have multiple classification pointing to the same
object. <<David agreed. I do say "Entities can have zero or more
classifications, that classify the entity">>
Page 9 "The classification associated with the term should not be automatically
cascaded by Atlas to the assigned assets." Agree that Atlas does not
necessarily needs to do the cascading because logic might need to be involved.
<<David agreed.>> However, the result might need to be made available in Atlas
and shown in a distinct way. If Atlas is seen as the single source of truth
then it must be possible for a end user to see from solely Atlas that a
classification is 'Derived from'. How that derivation has occurred can happen
by a different service. <<David Interesting thought. I would think that the
OMAS is the layer that needs to derive or cache these cascaded classifications
- it would help me to understand more on the use case requiring us to see the
OMAS view in the OMRS layer? >>
changes will be in the next document.
> 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)
