[
https://issues.apache.org/jira/browse/SENTRY-1627?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16023121#comment-16023121
]
Qianbo Huai commented on SENTRY-1627:
-------------------------------------
We are testing an implementation. The results are positive so far.
== Details ==
Sentry service loads the Viewfs mount table and understands the mapping between
viewfs paths and actual HDFS paths on individual Hadoop clusters. When a HDFS
sentry plugin fetches path and permission updates from sentry service, it calls
a modified thrift method so that it can identify itself to the sentry service.
In turn, the service converts the viewfs snapshot or delta path changes to what
are relevant to the requesting Hadoop cluster - paths belonging to different
clusters will be filtered out.
There are also some small changes on metastore plugin to support viewfs://
paths.
> Support viewfs in Sentry Namenode plugin
> ----------------------------------------
>
> Key: SENTRY-1627
> URL: https://issues.apache.org/jira/browse/SENTRY-1627
> Project: Sentry
> Issue Type: New Feature
> Components: Hdfs Plugin, Hive Plugin, Sentry
> Affects Versions: 1.5.1
> Reporter: Qianbo Huai
> Fix For: 1.5.1
>
>
> The View File System (ViewFs) provides a way to manage multiple Hadoop file
> system namespaces (or namespace volumes). It is particularly useful for
> clusters having multiple namenodes, and hence multiple namespaces, in HDFS
> Federation. ViewFs is analogous to client side mount tables in some
> Unix/Linux systems.
> In a ViewFs deployment, Sentry MetastorePlugin sees viewfs schemed paths but
> drops them in PathsUpdate.parsePath as it hardcodes the support for only hdfs
> schemed path.
> If paths updates are sent to Sentry Namenode plugin, the viewfs paths need to
> be converted to per-namenode (HDFS cluster) paths.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
