Support Questions
Find answers, ask questions, and share your expertise
Announcements
Alert: Welcome to the Unified Cloudera Community. Former HCC members be sure to read and learn how to activate your account here.

HDP 2.5: Apache Atlas 0.7 Tag attributes how to use?

Solved Go to solution

HDP 2.5: Apache Atlas 0.7 Tag attributes how to use?

New Contributor

I have installed Apache Atlas using Ambari and tried the Atlas + Ranger Integration using Tag. I don't understand about the Tag Attribute and its usage.

11454-tag-attribute.png

I have created attribute "word" but do not know how and when it is useful.

11455-tag-attribute-word.png

What is the purpose of tag attribute?.

Can anyone provide complete example of using Tag attributes and how it will be used in Atlas?.

I dont think tag attributes are useful in Ranger and it can be used only used within Atlas.

Thanks,

Uvaraj.S

1 ACCEPTED SOLUTION

Accepted Solutions

Re: HDP 2.5: Apache Atlas 0.7 Tag attributes how to use?

@Uvaraj Seerangan Please refer to the below tutorial which talks about the usage of tag based policies.

https://community.hortonworks.com/articles/33057/atlas-ranger-tutorial.html

2 REPLIES 2

Re: HDP 2.5: Apache Atlas 0.7 Tag attributes how to use?

@Uvaraj Seerangan Please refer to the below tutorial which talks about the usage of tag based policies.

https://community.hortonworks.com/articles/33057/atlas-ranger-tutorial.html

Highlighted

Re: HDP 2.5: Apache Atlas 0.7 Tag attributes how to use?

New Contributor

@Uvaraj Seerangan Please refer to this discussion on practical use for tag attributes and discussion on how to use them: https://community.hortonworks.com/questions/64496/what-is-a-real-world-example-of-using-attributes-o...

In the discussion, an example was provided that leverages tag attributes for the concept of a data lease or duration in which the entity is valid. For example, we could have tags called ACTIVE_AFTER, EXPIRES_ON both of which can have an attribute effective_date. On different entities we could then set different values of the effective_date attribute once we tag them with ACTIVE_AFTER or EXPIRES_ON tags. So different entities could have different validity dates through the values set for effective_date on the entity. This can be used to manage the period during which an asset is effective. Once entities are tagged, the tags and attributes flow down to Ranger and you can write a single security policy to prevent specific groups of users from accessing all assets tagged with EXPIRES_ON after the effective_date without having to write 1 policy per entity.

Don't have an account?
Coming from Hortonworks? Activate your account here