[
https://issues.apache.org/jira/browse/HDDS-341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16578578#comment-16578578
]
Elek, Marton commented on HDDS-341:
-----------------------------------
Thanks the detailed definition of the problem [~aw]
1. According to the original proposal of merging Ozone to Hadoop trunk, the
problem could be solved with deleting ozone files from the 3.2 branch (we need
trunk/3.2 separation for that):
>From Owen's mail:
{quote}
* On trunk (as opposed to release branches) HDSL will be a separate module in
Hadoop's source tree. This will enable the HDSL to work on their trunk and the
Hadoop trunk without making releases for every change.
* Hadoop's trunk will only build HDSL if a non-default profile is enabled.
* When Hadoop creates a release branch, the RM will delete the HDSL module from
the branch.
{quote}
I would be happy to help the RM of the 3.2 to do this.
2. I agree that the dependency on hadoop 3.2.0-SNAPSHOT is a real problem. The
main reason for the original proposal (merge ozone to hadoop trunk) was to make
it easier to use the latest hadoop all the time. I proposed in HDDS-214 to
release the required hadoop artifacts with an ozone specific version. (eg.
org.apache.hadoop:hadoop-common:ozone-0.2.1)
> HDDS/Ozone bits are leaking into Hadoop release
> -----------------------------------------------
>
> Key: HDDS-341
> URL: https://issues.apache.org/jira/browse/HDDS-341
> Project: Hadoop Distributed Data Store
> Issue Type: Bug
> Components: Ozone Manager
> Reporter: Anu Engineer
> Priority: Blocker
> Fix For: 0.2.1
>
>
> [~aw] in the Ozone release discussion reported that Ozone is leaking bits
> into Hadoop. This has to be fixed before Hadoop 3.2 or Ozone 0.2.1 release.
> I will make this a release blocker for Ozone.
>
> {noformat}
> >Has anyone verified that a Hadoop release doesn't have _any_ of the extra
> >ozone bits that are sprinkled outside the maven modules?
> [aengineer] : As far as I know that is the state, we have had multiple Hadoop
> releases after ozone has been merged. So far no one has reported Ozone bits
> leaking into Hadoop. If we find something like that, it would be a bug.
> [aw]: There hasn't been a release from a branch where Ozone has been merged
> yet. The first one will be 3.2.0. Running create-release off of trunk
> presently shows bits of Ozone in dev-support, hadoop-dist, and elsewhere in
> the Hadoop source tar ball.
> So, consider this as a report. IMHO, cutting an Ozone release prior to
> a Hadoop release ill-advised given the distribution impact and the
> requirements of the merge vote.
> {noformat}
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
