[
https://issues.apache.org/jira/browse/HDDS-1661?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16876610#comment-16876610
]
Elek, Marton commented on HDDS-1661:
------------------------------------
I would do it only after a clear consensus how HDDS and Ozone projects will be
used by HDFS. The real reason to use two separated projects (HDDS and Ozone) is
the possibility to release them and use them in two different way. HDDS
projects may or may not be used by HDFS project and may or may not be released
in a separated way.
The future is unknown, but what we know is that the there is now blocking
problem with the current approach. This Jira didn't define any problem just
that Ozone "some what fragmented" which seems to be an opinion.While I can see
some value to use a different approach (such as the suggested one) I would wait
with such big change until we will have more data about the future's plan.
.
> Consolidate hadoop-hdds and hadoop-ozone into hadoop-ozone-project
> ------------------------------------------------------------------
>
> Key: HDDS-1661
> URL: https://issues.apache.org/jira/browse/HDDS-1661
> Project: Hadoop Distributed Data Store
> Issue Type: Bug
> Reporter: Eric Yang
> Priority: Major
>
> Ozone source code is some what fragmented in Hadoop source code. The current
> code looks like:
> {code}
> hadoop/pom.ozone.xml
> ├── hadoop-hdds
> └── hadoop-ozone
> {code}
> It is helpful to consolidate the project into high level grouping such as:
> {code}
> hadoop
> └── hadoop-ozone-project/pom.xml
> └── hadoop-ozone-project/hadoop-hdds
> └── hadoop-ozone-project/hadoop-ozone
> {code}
> This allows user to build ozone from hadoop-ozone-project directory.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
