[
https://issues.apache.org/jira/browse/ATLAS-1980?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Radley updated ATLAS-1980:
--------------------------------
Description:
Using a model RelationshipDef that is defines
{
"name": "CategoryAnchor",
"typeVersion": "1.0",
"endDef1": {
"name": "categories",
"type": "Glossary",
"cardinality":"SET",
"isContainer":true
},
"endDef2": {
"name": "anchor",
"type": "GlossaryCategory",
"cardinality":"SINGLE"
},
"relationshipCategory":"COMPOSITION",
"propagateTags":"NONE"
},
- it does not check that the guid of the relationship is actually of the right
type. If I create an instance of the above relationships passing 2
GlossaryCategory guids ; it works. This should be rejected.
was:
Using a model RelationshipDef that is defines
{
"name": "CategoryAnchor",
"typeVersion": "1.0",
"endDef1": {
"name": "categories",
"type": "Glossary",
"cardinality":"SET",
"isContainer":true
},
"endDef2": {
"name": "anchor",
"type": "GlossaryCategory",
"cardinality":"SINGLE"
},
"relationshipCategory":"COMPOSITION",
"propagateTags":"NONE"
},
- I can create a relationship then add the same GlossayCategory to another
glossary. Both edges then exist. There should be only one allowed due to the
RelationshipDef cardinality. This should be rejected.
- it does not check that the guid of the relationship is actually of the right
type. If I create an instance of the above relationships passing 2
GlossaryCategory guids ; it works. This should be rejected.
Summary: Add relationship instance validation to check end point type
(was: Improve validations for relationships)
> Add relationship instance validation to check end point type
> ------------------------------------------------------------
>
> Key: ATLAS-1980
> URL: https://issues.apache.org/jira/browse/ATLAS-1980
> Project: Atlas
> Issue Type: Bug
> Reporter: David Radley
> Assignee: David Radley
> Attachments: ATLAS-1980.patch
>
>
> Using a model RelationshipDef that is defines
> {
> "name": "CategoryAnchor",
> "typeVersion": "1.0",
> "endDef1": {
> "name": "categories",
> "type": "Glossary",
> "cardinality":"SET",
> "isContainer":true
> },
> "endDef2": {
> "name": "anchor",
> "type": "GlossaryCategory",
> "cardinality":"SINGLE"
> },
> "relationshipCategory":"COMPOSITION",
> "propagateTags":"NONE"
> },
> - it does not check that the guid of the relationship is actually of the
> right type. If I create an instance of the above relationships passing 2
> GlossaryCategory guids ; it works. This should be rejected.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
