[
https://issues.apache.org/jira/browse/ATLAS-2444?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Madhan Neethiraj resolved ATLAS-2444.
-------------------------------------
Resolution: Fixed
Assignee: Apoorv Naik
Fix Version/s: 1.0.0
Committed to master:
http://git-wip-us.apache.org/repos/asf/atlas/commit/3ec37cae
> HDFS NameNode Federation support
> --------------------------------
>
> Key: ATLAS-2444
> URL: https://issues.apache.org/jira/browse/ATLAS-2444
> Project: Atlas
> Issue Type: Bug
> Reporter: Apoorv Naik
> Assignee: Apoorv Naik
> Priority: Major
> Fix For: 1.0.0
>
>
> With Hadoop 3, HDFS is introducing namespace/nameServiceId for data
> segregation.
> A cluster with hadoop 3 deployment can have multiple name nodes under a
> single name space and multiple namespace/nameserviceIds as well.
> This metadata can be captured for other interested application/parties, eg.
> Ranger can use this to enforce policies per Namespace.
>
> Changes:
>
> # HDFS model to include a new attribute called nameServiceId, default will
> be empty
> # hdfs path's qualified name will include the cluster info as well
> # All Hooks dealing with HDFS path will resolve the host:port to the
> respective nameServiceId
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
