You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@atlas.apache.org by "Apoorv Naik (JIRA)" <ji...@apache.org> on 2018/05/24 02:18:00 UTC
[jira] [Comment Edited] (ATLAS-2444) HDFS NameNode Federation
support
[ https://issues.apache.org/jira/browse/ATLAS-2444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16488313#comment-16488313 ]
Apoorv Naik edited comment on ATLAS-2444 at 5/24/18 2:17 AM:
-------------------------------------------------------------
Committed updates to following branch
* master: http://git-wip-us.apache.org/repos/asf/atlas/commit/bcd5bb60732833f000e8e50f1f16b2cf3dbc32c
* branch-1.0:
was (Author: apoorvnaik):
Committed updates to following branch
* master: [http://git-wip-us.apache.org/repos/asf/atlas/commit/|http://git-wip-us.apache.org/repos/asf/atlas/commit/3ec37cae]bcd5bb60732833f000e8e50f1f16b2cf3dbc32c
* branch-1.0:
> HDFS NameNode Federation support
> --------------------------------
>
> Key: ATLAS-2444
> URL: https://issues.apache.org/jira/browse/ATLAS-2444
> Project: Atlas
> Issue Type: Bug
> Reporter: Srikanth Venkat
> Assignee: Apoorv Naik
> Priority: Major
> Fix For: 1.0.0
>
>
> With Hadoop 3, HDFS supports multiple namespaces; each namespace is serviced by a cluster of name-nodes identified by a nameServiceId. HDFS path entity in Atlas should be updated to capture the the nameServiceId of the namenode cluster for the path. Also, references to individual namenode in the path should be replaced with corresponding nameServiceID.
> 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)