hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Anu Engineer (JIRA)" <j...@apache.org>
Subject [jira] [Created] (HDDS-341) HDDS/Ozone bits are leaking into Hadoop release
Date Wed, 08 Aug 2018 21:23:00 GMT
Anu Engineer created HDDS-341:

             Summary: 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

[~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.

>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.  


This message was sent by Atlassian JIRA

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

View raw message