how to create a policy that prohibits combination of datasets

[#1]

On the Hortonworks blog http://hortonworks.com/blog/the-next-generation-of-hadoop-based-security-data-governance/

One of the features of Atlas/Ranger is to Prohibit the combination of datasets. The blog says:

"4. Prohibition against dataset combinations: With Atlas/ Ranger integration, it is now possible to define a security policy that restricts combining two data sets. For example, if one column consists of customer’s account numbers and the other customer names. These column may be in compliance individually, but pose a violation if combined as part of a query. Administrators can now apply a metadata tag to both data sets to prevent them from being combined, helping avoid privacy violation."

What options in Atlas/Ranger should I use to prevent the combination of data sets?

[#2 · Accepted solution]

@cduby I published an HCC article on this topic, please see: https://community.hortonworks.com/articles/63664/how-to-create-a-ranger-policy-that-prohibits-combi....