[
https://issues.apache.org/jira/browse/HDFS-15701?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17241786#comment-17241786
]
Steve Loughran commented on HDFS-15701:
---------------------------------------
usual constraints: specification docs, contract tests, pathCapabilities probe
if its an optional feature.
javadocs for FileSystem list some things you need to update. HBase's HBoss will
need some changes too.
> Add resolveMountPath API in FileSystem
> --------------------------------------
>
> Key: HDFS-15701
> URL: https://issues.apache.org/jira/browse/HDFS-15701
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Components: fs, ViewHDFS
> Affects Versions: 3.4.0
> Reporter: Uma Maheswara Rao G
> Assignee: Uma Maheswara Rao G
> Priority: Major
>
> Currently FileSystem has an API resolvePath. To know where the path has
> mounted, the applications can use that API as the retuned path is from actual
> target path in the case of mount file systems like ViewFS,
> ViewFSOverloadScheme or ViewDistributedFileSystem.
> However, resolvePath does more than what is needed by Apps when they want to
> know where the path has mounted. It's because resolvePath internally calls
> "getFileStatus".
> This additional call is unnecessary when apps just want to where the path
> mounted.
> Since we have mounted filesystems available in FS, I think it's good to add
> resolveMountPath API, which will just do the following.
> If the fs is mounted fs, then it will resolve it's mount tables and return
> the actual target path. If the fs is non mounted, then it will simply return
> the same path.
> Currently Applications like Hive, Ranger using resolvePath API. ( this is
> forcing to do additional RPC internally)
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
