From hdfs-issues-return-228888-archive-asf-public=cust-asf.ponee.io@hadoop.apache.org Thu Aug 9 16:53:06 2018 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx-eu-01.ponee.io (Postfix) with SMTP id 8EFBF18078F for ; Thu, 9 Aug 2018 16:53:05 +0200 (CEST) Received: (qmail 34421 invoked by uid 500); 9 Aug 2018 14:53:04 -0000 Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list hdfs-issues@hadoop.apache.org Received: (qmail 34236 invoked by uid 99); 9 Aug 2018 14:53:04 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 09 Aug 2018 14:53:04 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id CD0CC1807BC for ; Thu, 9 Aug 2018 14:53:03 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -110.301 X-Spam-Level: X-Spam-Status: No, score=-110.301 tagged_above=-999 required=6.31 tests=[ENV_AND_HDR_SPF_MATCH=-0.5, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, USER_IN_DEF_SPF_WL=-7.5, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id mpufAj1WMe8O for ; Thu, 9 Aug 2018 14:53:03 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id 7D32B5F563 for ; Thu, 9 Aug 2018 14:53:02 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 9E539E0239 for ; Thu, 9 Aug 2018 14:53:01 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id A501D23FA9 for ; Thu, 9 Aug 2018 14:53:00 +0000 (UTC) Date: Thu, 9 Aug 2018 14:53:00 +0000 (UTC) From: "Elek, Marton (JIRA)" To: hdfs-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HDDS-341) HDDS/Ozone bits are leaking into Hadoop release MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/HDDS-341?page=3Dcom.atlassian.j= ira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D165749= 46#comment-16574946 ]=20 Elek, Marton commented on HDDS-341: ----------------------------------- Is it a problem with binary or source distribution [~aw]? As I understand w= e decided to manage hadoop and ozone in the same source tree and ozone is p= art of the hadoop trunk. Not sure if it's a problem to include some ozone s= pecific source in a hadoop source releases. If it is, we can remove the ozo= ne sources from 3.2 branch after a trunk/3.2 branch separation.=20 Ozone release will contain all the sources from the trunk according to the = current plan (including hadoop/hdfs/yarn/mapreduce sources) > 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=C2=A0 Hadoop 3.2 or Ozone 0.2.1 r= elease. I will make this a release blocker for Ozone. > =C2=A0 > {noformat} > >Has anyone verified that a Hadoop release doesn't have _any_ of the extr= a ozone bits that are sprinkled outside the maven modules? > [aengineer] : As far as I know that is the state, we have had multiple Ha= doop 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 bu= g. > [aw]:=09There hasn't been a release from a branch where Ozone has been me= rged yet. The first one will be 3.2.0.=C2=A0=C2=A0Running create-release of= f of trunk presently shows bits of Ozone in dev-support, hadoop-dist, and e= lsewhere in the Hadoop source tar ball. > =09So, consider this as a report. IMHO, cutting an Ozone release prior to= a Hadoop release ill-advised given the distribution impact and the require= ments of the merge vote.=C2=A0=C2=A0 > {noformat} > =C2=A0 -- This message was sent by Atlassian JIRA (v7.6.3#76005) --------------------------------------------------------------------- To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org