Support Questions

Find answers, ask questions, and share your expertise

Apache Atlas use of "Constraints" to change typeDef behaviour?

New Contributor


I'm working on establishing a data catalogue in Atlas with bespoke typeDefs, and we have a requirement to change whether some entity attributes are optional or mandatory based on the values of the value of another attribute.  Looking through the documentation I can see that "Constraints" have several types as mentioned in this post here (Solved: Re: Apache Atlas Types System V2 - Cloudera Community - 206759), but I can't understand which type of constraint would be the correct one for the job, or how it would need to be defined in the typeDef, but something along these lines?

"params":{"1":"...", "2":"..."},
"type":"ownedRef | inverseRef | attribute | etc..."

Any help would be appreciated!