Support Questions

Find answers, ask questions, and share your expertise
Announcements
Celebrating as our community reaches 100,000 members! Thank you!

When creating a view in Hive that includes an Atlas tagged column, why is the view not restricted by the same policy as it's source table?

avatar
Guru

When I have a table in Atlas which blocks a user from selecting on the ssn column of table1, I create a view (view1) which has ssn as a column and then I am able to select * on view1 with the user that would have been denied select * on table1.

Is there a way to ensure that all downstream tables / views cary the same policy as their parent?

Or is this the expected and desired behavior?

1 ACCEPTED SOLUTION

avatar
hide-solution

This problem has been solved!

Want to get a detailed solution you have to login/registered on the community

Register/Login
5 REPLIES 5

avatar
hide-solution

This problem has been solved!

Want to get a detailed solution you have to login/registered on the community

Register/Login

avatar
Guru

Good to know. Thanks for clearing that up for me.

avatar
Rising Star

Update: The tag propagation feature (ATLAS-1821) was released as part of HDP 3.0.0.

avatar
Explorer

Both column level lineage as well as tag propagation are roadmap items

@Erik Bergenholtz any guess on the release date with this feature ?

avatar

If you are in the quest for the best portal to have one of the best web browser so here it is firefox downloads which will meet your all requirements which you may be seeking for. This browser provides exact results to your searches within the short period of time.