You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ozone.apache.org by "Ryan Blough (Jira)" <ji...@apache.org> on 2026/05/27 21:10:00 UTC

[jira] [Resolved] (HDDS-12853) Look at feature parity between bucket browser and HDFS file browser

     [ https://issues.apache.org/jira/browse/HDDS-12853?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ryan Blough resolved HDDS-12853.
--------------------------------
    Resolution: Invalid

This would entail work on proprietary components, and is outside the scope of Apache Ozone work.

> Look at feature parity between bucket browser and HDFS file browser
> -------------------------------------------------------------------
>
>                 Key: HDDS-12853
>                 URL: https://issues.apache.org/jira/browse/HDDS-12853
>             Project: Apache Ozone
>          Issue Type: Improvement
>    Affects Versions: 1.3.0, 1.4.0, 1.4.1
>            Reporter: Ryan Blough
>            Priority: Major
>
> Coming to Ozone from HDFS entails a noticeable gap in terms of the granularity and completeness of tools for browsing, monitoring, and options for how to do tasks. I think taking a look at closing this gap explicitly is a good idea.
> This issue was motivated by an extended series of conversations with a large enterprise user of Ozone. They are running Ozone in a multi-tenanted cluster, with both internal teams and external clients who are themselves large enterprises. The use-case is a direct replacement for HDFS, with the goals of larger scaling and better performance for lots of simultaneous jobs. The issue is that while the people running the Ozone cluster are fairly well informed and understanding of tradeoffs and the difference in maturity of the products, the end-users they provide for are less so. A particular sore point is that their methods of monitoring, measuring, and controlling have changed under Ozone, and many things they expect and have come to rely on aren't available yet.
> I expect this to be generally true, and for most people deploying Ozone for use by _other_ groups of people to have similar experiences, especially when Ozone is directly replacing HDFS.
> The users I spoke to have some concrete requests, which I will file as children of this ticket; I raised this parent ticket so we can link other concrete requests as they come in, or link existing jiras that meet the description of providing a feature also provided by HDFS File Browser.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@ozone.apache.org
For additional commands, e-mail: issues-help@ozone.apache.org