You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ozone.apache.org by "Marton Elek (Jira)" <ji...@apache.org> on 2021/08/19 07:32:00 UTC
[jira] [Comment Edited] (HDDS-5447) HttpFS support in Ozone
[ https://issues.apache.org/jira/browse/HDDS-5447?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17401505#comment-17401505 ]
Marton Elek edited comment on HDDS-5447 at 8/19/21, 7:31 AM:
-------------------------------------------------------------
> WebHDFS REST API is a well established API that uses the Hadoop FileSystem API to access anything that has a FileSystem API. A Hadoop HTTPFS server can be configured even today to use ofs:// file system scheme to connect to Ozone, it is just hard to manage and pull in a good amount of HDFS dependencies, and use HDFS lifecycle scripts to configure and run
Thanks to explain it [~pifta]. I understand the pain with the Hadoop install, but still it seems to be an independent effort from Ozone. Especially as
* Ozone already offers a REST API
* WebHDFS is generic, not specific to Ozone
I would consider moving this effort to the Hadoop project itself. To simplify the problem, we can propose a separated apache/hadoop-webhdfs project, which provides a standalone REST gateway for any Hadoop Compatible File System.
This approach provides an easy way to start WebHDFS together with Ozone without installing HDFS, but doesn't require duplicated effort to maintain the code.
What do you think?
was (Author: elek):
> WebHDFS REST API is a well established API that uses the Hadoop FileSystem API to access anything that has a FileSystem API. A Hadoop HTTPFS server can be configured even today to use ofs:// file system scheme to connect to Ozone, it is just hard to manage and pull in a good amount of HDFS dependencies, and use HDFS lifecycle scripts to configure and run
Thanks to explain it [~pifta]. I understand the pain with the Hadoop install, but still it seems to be an independent effort from Ozone. Especially as * Ozone already offers a REST API
* WebHDFS is generic, not specific to Ozone
I would consider moving this effort to the Hadoop project itself. To simplify the problem, we can propose a separated apache/hadoop-webhdfs project, which provides a standalone REST gateway for any Hadoop Compatible File System.
This approach provides an easy way to start WebHDFS together with Ozone without installing HDFS, but doesn't require duplicated effort to maintain the code.
What do you think?
> HttpFS support in Ozone
> -----------------------
>
> Key: HDDS-5447
> URL: https://issues.apache.org/jira/browse/HDDS-5447
> Project: Apache Ozone
> Issue Type: New Feature
> Components: Ozone Client, Ozone Manager
> Reporter: Aravindan Vijayan
> Assignee: István Fajth
> Priority: Major
> Attachments: HTTPFS interface for Ozone.pdf
>
>
> There are several tools out there mainly written in Python, that uses the webhdfs interface to connect to HDFS. Even there are quite a few other filesystem implementations that provide access via the same rest interface that HDFS provides.
> HUE also implements the HDFS file browser by accessing HDFS via the REST API either on the NameNodes or on HTTPFS Server instances added to the HDFS service.
> This gave the inspiration to check and experiment what is required to support a similar REST endpoint over Ozone.
> The advantage is that we can ease the migration of tools developed in-house that are using this interface of HDFS, while we can add the possibility to browse Ozone from HUE.
> There is literally no disadvantage of having such an interface, as we can implement it as a separate module which does not have any interference with the rest of the code, as the REST endpoint as with HTTPFS will use a regular Java based Ozone client to serve any requests.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@ozone.apache.org
For additional commands, e-mail: issues-help@ozone.apache.org