[
https://issues.apache.org/jira/browse/HDFS-9055?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14741133#comment-14741133
]
Haohui Mai commented on HDFS-9055:
----------------------------------
Can you elaborate where and how WebHDFS v1 is broken? Do you have a design that
can be posted?
I can see two types of jiras from the related jiras listed above:
* WebHDFS does not expose some NN functionalities. (quota, snapshots, etc.)
* New functionalities via WebHDFS that might require help in the NN side (e.g.,
find, recursive list)
For the first type of jiras they are basically NN RPC calls. Currently we add
new WebHDFS call whenever we need to make WebHDFS to support the same NN RPC
calls manually. This is not scalable from the maintenance points of view. I
believe a cleaner approach is to expose the RPC in a Web-friendly protocol like
GRPC instead of doing every single call by hand.
For the second type of jiras, particularly the find and lsr, they obviously
require processing directories recursively. It should not be done at the NN
side to avoid blocking other requests. We did that at the client side today
through DFSClient, IMO WebHDFS should follow the same approach.
> WebHDFS REST v2
> ---------------
>
> Key: HDFS-9055
> URL: https://issues.apache.org/jira/browse/HDFS-9055
> Project: Hadoop HDFS
> Issue Type: New Feature
> Components: webhdfs
> Affects Versions: 3.0.0
> Reporter: Allen Wittenauer
>
> There's starting to be enough changes to fix and add missing functionality to
> webhdfs that we should probably update to REST v2. This also gives us an
> opportunity to deal with some incompatible issues.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
