Details
-
Improvement
-
Status: Closed
-
Major
-
Resolution: Fixed
-
None
-
None
-
None
Description
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
Attachments
Attachments
Issue Links
- Blocked
-
ATLAS-1459 Atlas V2 types to manage bidirectional relationships
- Resolved
-
ATLAS-1690 Introduce top level relationships
- Resolved
-
ATLAS-1692 Introduce the ability to relate a type to any type
- Closed
- contains
-
ATLAS-1211 Classifications : Support subclasifications & ordering
- Resolved
- depends upon
-
ATLAS-1839 Area 3 of the open metadata model - including the Glossary
- Closed
- relates to
-
ATLAS-1689 Virtual Data Connector Project
- Closed
- supercedes
-
ATLAS-1213 Doc: Explain key terms used in information governance
- Open
1.
|
Add constraints to JAVA API | Closed | Unassigned | |
2.
|
Create Subject Area OMAS API | Resolved | David Radley | |
3.
|
Add REST API | Closed | Unassigned | |
4.
|
Swagger | Resolved | Unassigned | |
5.
|
documentation | Closed | Unassigned | |
6.
|
amend Atlas simple security to add glossary | Resolved | Unassigned | |
7.
|
amend Atlas simple security to add glossary | Resolved | Unassigned | |
8.
|
Update Atlas UI to use V2 Glossary | Resolved | Unassigned |