[
https://issues.apache.org/jira/browse/ATLAS-1700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Radley updated ATLAS-1700:
--------------------------------
Description:
Add constraints to JAVA API for the Glossary. There are some constraints that
can be captured using the constraints in the type model. For the Glossary API,
there are restrictions that cannot be captured in the type model. I am thinking
of constraints like:
- policing that we do not allow a category to be updated to have a parent as
one of its descendants.
- policing that we do not allow a category from another glossary to be added
under our category
- policing that we do not allow a category to be updated, such that the
category tree contains categories from more than one glossary.
- restricting terms under a category to have unique names (we need to get
consensus as to whether this is something we would like)
These sorts of restrictions need to policed in the Java code - as there is no
place for them in the model. For the Glossary, we are looking to add a new OMAS
layer around the base Atlas entity APIs.
was:
Add constraints to JAVA API for the Glossary. There are some constraints that
can be captured using the constraints in the type model. For the Glossary API,
there are restrictions that cannot be captured in the type model. I am thinking
of constraints like:
- policing that we do not allow a category to be updated to have a parent as
one of its descendants.
- policing that we do not allow a category from another glossary to be added
under out category
- policing that we do not allow a category to be updated such that the category
tree contains categories from more than one glossary.
- restricting terms under a category to have unique names (we need to get
consensus as to whether this is something we would like)
These sorts of restrictions would need to policed in the Java code - as there
is no place for them in the model. For the Glossary, we are looking to add a
new OMAS layer around the base Atlas entity APIs.
> Add constraints to JAVA API
> ---------------------------
>
> Key: ATLAS-1700
> URL: https://issues.apache.org/jira/browse/ATLAS-1700
> Project: Atlas
> Issue Type: Sub-task
> Reporter: David Radley
> Labels: VirtualDataConnector
>
> Add constraints to JAVA API for the Glossary. There are some constraints that
> can be captured using the constraints in the type model. For the Glossary
> API, there are restrictions that cannot be captured in the type model. I am
> thinking of constraints like:
> - policing that we do not allow a category to be updated to have a parent as
> one of its descendants.
> - policing that we do not allow a category from another glossary to be added
> under our category
> - policing that we do not allow a category to be updated, such that the
> category tree contains categories from more than one glossary.
> - restricting terms under a category to have unique names (we need to get
> consensus as to whether this is something we would like)
>
> These sorts of restrictions need to policed in the Java code - as there is no
> place for them in the model. For the Glossary, we are looking to add a new
> OMAS layer around the base Atlas entity APIs.
>
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
