[
https://issues.apache.org/jira/browse/HDFS-13469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16459854#comment-16459854
]
Chris Douglas commented on HDFS-13469:
--------------------------------------
bq. We can't close a serious oversight/regression in the router by essentially
throwing TooHardToSupportException.
Exposing and addressing inodes through a magic path is not just hard to extend,
it's impossible without compromising compatibility. Option one, we bypass the
restricted ID space by changing the abstraction: add explicit, opaque handles
to files/directories and use those for directory enumeration/traversal,
fetching block locations, etc. Option two, we hack it into inodeid and continue
using the magic path. If there are other options then let's explore them, but
the constraints are understood and don't need to be belabored.
HDFS-7878 was attempting to introduce option one. It's only in 3.1.0, so if it
requires extension/modification to serve that purpose then let's do it. Option
two has tradeoffs, as in HDFS-10867. How would you like to address this for RBF?
> RBF: Support InodeID in the Router
> ----------------------------------
>
> Key: HDFS-13469
> URL: https://issues.apache.org/jira/browse/HDFS-13469
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Reporter: Íñigo Goiri
> Priority: Major
>
> The Namenode supports identifying files through inode identifiers.
> Currently the Router does not handle this properly, we need to add this
> functionality.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
