Hi, I'm implementing a data catalogue in Atlas with bespoke typeDefs, and we have the requirement to hide some entity attributes from some users, as well as hiding some entity types themselves.  We can do this at the entity level by applying Classifications at the entity level, and using the tagSync to Ranger to block access to unauthorised entities. Is it possible to apply Classifications at the attribute level of a typeDef or when defining an entity?  I've tried it and it doesn't appear possible, but any confirmation of this would be much appreciated! Assuming that classifications cannot be applied at the attribute level, is there another way of limiting user access to attributes, other than separating the attributes into separate entities?  I've seen the "Options" parameters in the typeDef, however there's no documentation I can find that gives further detail on what can be defined in Options, nor any examples for implementing. Many thanks, Rob ... View more

Hi, 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? "constraints":[{ "params":{"1":"...", "2":"..."}, "type":"ownedRef | inverseRef | attribute | etc..." }] Any help would be appreciated! Rob ... View more