[ https://issues.apache.org/jira/browse/ATLAS-1211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Madhan Neethiraj updated ATLAS-1211: ------------------------------------ Fix Version/s: 1.0.0 > Classifications : Support subclasifications & ordering > ------------------------------------------------------ > > Key: ATLAS-1211 > URL: https://issues.apache.org/jira/browse/ATLAS-1211 > Project: Atlas > Issue Type: New Feature > Reporter: Nigel Jones > Priority: Major > Fix For: 1.0.0 > > > Governance classifications may be ordered and contain sub-classifications. > For example a classification "confidentiality" may contain an *ordered* set > of values such as > - unclassified > - internal use > - confidential > - sensitive > - restricted > - top secret > The ordering is a logical progression -- going from the least confidential to > the most confidential. > When these governance classifications are retrieved or checked against we may > wish to performance range checks. For example in a ranger policy we may wish > to do the equivilent of "if confidentiality >= confidential then.." > Furthermore these classifications may be hierarchical. The mail thread below > uses the example "confidential/business confidential" and > "confidential/personal confidential". these are at an equivilent level, but > different > Atlas should be extended to support this.(further JIRAs would be needed to > update ranger) > In terms of implementation, For existing apis/tag integration we may consider > a form of flattening or overloading the name to ease migration. > Note that this will prereq the anticipated work on ATLAS-1187 to introduce > classifications, but I've split this further development out so that we can > get a first pass done in 1187 > This suggestion first came up in the mailing list discussion on "Rename Trait > to classification", which relates to ATLAS-1187 - also viewable on gmane at > news://news.gmane.org:119/nt0jdp$ml0$1...@blaine.gmane.org -- This message was sent by Atlassian JIRA (v7.6.3#76005)