Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 2F3B62009D9 for ; Wed, 18 May 2016 07:08:23 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 2CC3A160A23; Wed, 18 May 2016 05:08:23 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 03596160A09 for ; Wed, 18 May 2016 07:08:21 +0200 (CEST) Received: (qmail 32221 invoked by uid 500); 18 May 2016 05:08:21 -0000 Mailing-List: contact yarn-dev-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list yarn-dev@hadoop.apache.org Received: (qmail 32195 invoked by uid 99); 18 May 2016 05:08:20 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 18 May 2016 05:08:20 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id 31AA9C74DA; Wed, 18 May 2016 05:08:20 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 1.448 X-Spam-Level: * X-Spam-Status: No, score=1.448 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, HTML_MESSAGE=2, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001] autolearn=disabled Authentication-Results: spamd1-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id YCDtpU3iCwlO; Wed, 18 May 2016 05:08:17 +0000 (UTC) Received: from mail-vk0-f47.google.com (mail-vk0-f47.google.com [209.85.213.47]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTPS id C9BAB5F1E7; Wed, 18 May 2016 05:08:16 +0000 (UTC) Received: by mail-vk0-f47.google.com with SMTP id z184so47298479vkg.0; Tue, 17 May 2016 22:08:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=KrtMWXGb0vMes8UrpVoTxn0DZAcRhbtZfz560FK5QDU=; b=bGKlnuIvFZHtvihabnH7hqMr4QfQqxx8Ycw6vurZtqZ3BRACb7eAcwGXdA/mMzSblt Bx14QxF62XZJpZjJcywB95RVxSm7KJLaP8YiZysK7rNok8wlVj/T8bHpJa1RrDCtYol4 okotpMJtT/EbsFwxQQTcH6gwYVLYk1RdPwJ9eO+SqS6GHCNwk4MCeeC3wEzDxgl0wbqg n3fPqZJFvhmiHxz2D0n6HVxmWrFl6pPt7uhfPv9OsM5wuPLp7k2iUxmOfl1fz728Shhz h/M8efC8mxzDn9EOjUzJk95BOKiF6nxrVvw0K1QF0uE+MMP6ngkVrVj4vWHVyqwOaFpS FmxA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc; bh=KrtMWXGb0vMes8UrpVoTxn0DZAcRhbtZfz560FK5QDU=; b=Ht7pD4u3d69udbF7QXROhuCCSy2dktnzNLQ2qkXKvNfgzNnl6aUXMhm6lD0EOr50j9 s6JdXyaNpP//0WQ/w3aAkKNjuk7Ljm/T+8QpZ1Q9deuXAuqTQyi/uMTbbeuCns7gogcu WweUfBNHrm89He7WpoBbcrDq3BQ/LPF+q5OkDPdczKEHaDNQtUBSoWl+o1vK/h7hrYw9 cgtUku2rngErVs8JUWurUehQsC1NnMoA0C1O4v0hqrXDUN1i8TB85+SqJayi1QZjhKID 4IUCrpsruMRld3CQK3xUFrVfOXP2WdQXZPaRmV6c40p/ahmdC7pbwNypP1aasjHmY5DZ Tchg== X-Gm-Message-State: AOPr4FU/qE18G8ZF0NHbHeNUSV33YvG7ywzO7kk4TIxYY5T6oT4/j5Zm/LCUXIc/wHpJBEqeRsrc3UyTGwbgHg== MIME-Version: 1.0 X-Received: by 10.31.52.147 with SMTP id b141mr2433235vka.78.1463548096234; Tue, 17 May 2016 22:08:16 -0700 (PDT) Received: by 10.31.94.129 with HTTP; Tue, 17 May 2016 22:08:16 -0700 (PDT) In-Reply-To: <2ec193c3-d65f-ae2c-f965-b1ad971bb87f@oss.nttdata.co.jp> References: <1463444626952.69346@hortonworks.com> <429bb01b-b140-4b51-ceff-4a1586203b4a@apache.org> <0db18ff8-7ea7-3f4f-ce91-3c0c9143e14c@apache.org> <31089D1A-809E-472E-9DB5-7380840DB36A@apache.org> <2ec193c3-d65f-ae2c-f965-b1ad971bb87f@oss.nttdata.co.jp> Date: Tue, 17 May 2016 22:08:16 -0700 Message-ID: Subject: Re: Different JIRA permissions for HADOOP and HDFS From: Yufei Gu To: Akira AJISAKA Cc: common-dev@hadoop.apache.org, "yarn-dev@hadoop.apache.org" Content-Type: multipart/alternative; boundary=001a1143f846634f0f053316d890 archived-at: Wed, 18 May 2016 05:08:23 -0000 --001a1143f846634f0f053316d890 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable I guess I lost my contributor role in HDFS, since I cannot comment in HDFS. Best, Yufei On Tue, May 17, 2016 at 9:48 PM, Akira AJISAKA wrote: > In HADOOP/HDFS/MAPREDUCE/YARN, I removed the administrators from > contributor group. After that, added Varun into contributor roles. > # Ray is already added into contributor roles. > > Hi contributors/committers, please tell me if you have lost your roles by > mistake. > > > just remove a big chunk of the committers from all the lists > In Apache Hadoop Project bylaws, "A Committer is considered emeritus by > their own declaration or by not contributing in any form to the project f= or > over six months." Therefore we can remove them from the list, but I'm > thinking this is the last option. > > Regards, > Akira > > > On 5/18/16 09:07, Allen Wittenauer wrote: > >> >> We should probably just remove a big chunk of the committers from all th= e >> lists. Most of them have disappeared from Hadoop anyway. (The 55% grow= th >> in JIRA issues in patch available state in the past year alone a pretty >> good testament to that fact.) >> >> On May 17, 2016, at 4:40 PM, Akira Ajisaka wrote: >>> >>> Is there some way for us to add a "Contributors2" group with the same >>>> permissions as a workaround? Or we could try to clean out contributor= s >>>> who are no longer active, but that might be hard to figure out. >>>> >>> >>> Contributors2 seems fine. AFAIK, committers sometimes cleaned out >>> contributors who are no longer active. >>> http://search-hadoop.com/m/uOzYt77s6mnzcRu1/v=3Dthreaded >>> >>> Another option: Can we remove committers from contributor group to >>> reduce the number of contributors? I've already removed myself from >>> contributor group and it works well. >>> >>> Regards, >>> Akira >>> >>> On 5/18/16 03:16, Robert Kanter wrote: >>> >>>> We've also had a related long-standing issue (or at least I have) wher= e >>>> I can't add any more contributors to HADOOP or HDFS because JIRA times >>>> out on looking up their username. I'm guessing we have too many >>>> contributors for those projects. I bet YARN and MAPREDUCE are close. >>>> Is there some way for us to add a "Contributors2" group with the same >>>> permissions as a workaround? Or we could try to clean out contributor= s >>>> who are no longer active, but that might be hard to figure out. >>>> >>>> - Robert >>>> >>>> On Tue, May 17, 2016 at 11:12 AM, Ray Chiang >>> > wrote: >>>> >>>> Similar issue for me. I can't modify HDFS and HADOOP JIRAs now. >>>> >>>> -Ray >>>> >>>> >>>> On Tue, May 17, 2016 at 9:54 AM, Varun Saxena >>>> > >>>> wrote: >>>> >>>> > Hi, >>>> > >>>> > I do not have permissions for any project other than YARN as well= . >>>> Unable >>>> > to assign a JIRA in MAPREDUCE for instance. >>>> > Can somebody give me permission ? >>>> > >>>> > Regards, >>>> > Varun Saxena. >>>> > >>>> > >>>> > On Tue, May 17, 2016 at 11:03 AM, Vinayakumar B < >>>> > vinayakumarb.apache@gmail.com >>>> > wrote: >>>> > >>>> > > Thanks Akira. >>>> > > On 17 May 2016 10:59, "Akira Ajisaka" >>> > wrote: >>>> > > >>>> > > > Hi Vinay, >>>> > > > >>>> > > > Added you into committer roles for HADOOP/MAPREDUCE/YARN. >>>> > > > >>>> > > > Regards, >>>> > > > Akira >>>> > > > >>>> > > > On 5/17/16 13:45, Vinayakumar B wrote: >>>> > > > >>>> > > >> Hi Junping, >>>> > > >> >>>> > > >> It looks like, I too dont have permissions in projects excep= t >>>> HDFS. >>>> > > >> >>>> > > >> Please grant me also to the group. >>>> > > >> >>>> > > >> Thanks in advance, >>>> > > >> -Vinay >>>> > > >> On 17 May 2016 6:10 a.m., "Sangjin Lee" >>> > wrote: >>>> > > >> >>>> > > >> Thanks Junping! It seems to work now. >>>> > > >> >>>> > > >> On Mon, May 16, 2016 at 5:22 PM, Junping Du >>>> > >>>> > > wrote: >>>> > > >> >>>> > > >> Someone fix the permission issue so that Administrator, >>>> committer and >>>> > > >>> reporter can edit the issue now. >>>> > > >>> >>>> > > >>> Sangjin, it sounds like you were not in JIRA's committer >>>> list before >>>> > > and >>>> > > >>> I >>>> > > >>> just add you into committer roles for 4 projects. Hope it >>>> works for >>>> > > >>> you now.=E2=80=8B >>>> > > >>> >>>> > > >>> >>>> > > >>> Thanks, >>>> > > >>> >>>> > > >>> >>>> > > >>> Junping >>>> > > >>> ------------------------------ >>>> > > >>> *From:* sjlee0@gmail.com >>>> > on behalf of Sangjin >>>> > Lee < >>>> > > >>> sjlee@apache.org > >>>> > > >>> *Sent:* Monday, May 16, 2016 11:43 PM >>>> > > >>> *To:* Zhihai Xu >>>> > > >>> *Cc:* Junping Du; Arun Suresh; Zheng, Kai; Andrew Wang; >>>> > > >>> common-dev@hadoop.apache.org >>>> ; yarn-dev@hadoop.apache.org >>>> >>>> > > >>> >>>> > > >>> *Subject:* Re: Different JIRA permissions for HADOOP and HD= FS >>>> > > >>> >>>> > > >>> I also find myself unable to edit most of the JIRA fields, >>>> and that >>>> > is >>>> > > >>> across projects (HADOOP, YARN, MAPREDUCE, and HDFS). >>>> Commenting and >>>> > the >>>> > > >>> workflow buttons seem to work, however. >>>> > > >>> >>>> > > >>> On Mon, May 16, 2016 at 8:14 AM, Zhihai Xu >>> > wrote: >>>> > > >>> >>>> > > >>> Great, Thanks Junping! Yes, the JIRA assignment works for m= e >>>> now. >>>> > > >>>> >>>> > > >>>> zhihai >>>> > > >>>> >>>> > > >>>> On Mon, May 16, 2016 at 5:29 AM, Junping Du >>>> > >>>> > > >>>> wrote: >>>> > > >>>> >>>> > > >>>> Zhihai, I just set you with committer permissions on >>>> MAPREDUCE JIRA. >>>> > > >>>>> >>>> > > >>>> Would >>>> > > >>>> >>>> > > >>>>> you try if the JIRA assignment works now? I cannot help o= n >>>> Hive >>>> > > >>>>> >>>> > > >>>> project. It >>>> > > >>>> >>>> > > >>>>> is better to ask hive project community for help. >>>> > > >>>>> For Arun's problem. from my check, the Edit permission on >>>> JIRA only >>>> > > >>>>> authorized to Administrator only. I don't know if this >>>> setting is >>>> > by >>>> > > >>>>> intention but it was not like this previously. >>>> > > >>>>> Can someone who make the change to clarify why we need >>>> this change >>>> > or >>>> > > >>>>> revert to whatever it used to be? >>>> > > >>>>> >>>> > > >>>>> Thanks, >>>> > > >>>>> >>>> > > >>>>> Junping >>>> > > >>>>> ________________________________________ >>>> > > >>>>> From: Arun Suresh >>> > >>>> > > >>>>> Sent: Monday, May 16, 2016 9:42 AM >>>> > > >>>>> To: Zhihai Xu >>>> > > >>>>> Cc: Zheng, Kai; Andrew Wang; common-dev@hadoop.apache.org >>>> ; >>>> > > >>>>> yarn-dev@hadoop.apache.org >>> yarn-dev@hadoop.apache.org> >>>> > > >>>>> Subject: Re: Different JIRA permissions for HADOOP and HD= FS >>>> > > >>>>> >>>> > > >>>>> Not sure if this is related.. but It also looks like I am >>>> now no >>>> > > longer >>>> > > >>>>> allowed to modify description and headline of JIRAs >>>> anymore.. >>>> > > >>>>> Would appreciate greatly if someone can help revert this = ! >>>> > > >>>>> >>>> > > >>>>> Cheers >>>> > > >>>>> -Arun >>>> > > >>>>> >>>> > > >>>>> On Mon, May 16, 2016 at 1:21 AM, Zhihai Xu >>>> > >>>> > wrote: >>>> > > >>>>> >>>> > > >>>>> Currently I also have permission issue to access the JIRA= . >>>> I can't >>>> > > >>>>>> >>>> > > >>>>> assign >>>> > > >>>> >>>> > > >>>>> the JIRA(I created) to myself. For example, >>>> > > >>>>>> https://issues.apache.org/jira/browse/MAPREDUCE-6696 and >>>> > > >>>>>> https://issues.apache.org/jira/browse/HIVE-13760. I can'= t >>>> find >>>> > the >>>> > > >>>>>> >>>> > > >>>>> button >>>> > > >>>>> >>>> > > >>>>>> to assign the JIRA to myself. >>>> > > >>>>>> I don't have this issue two three weeks ago. Did anythin= g >>>> change >>>> > > >>>>>> >>>> > > >>>>> recently? >>>> > > >>>>> >>>> > > >>>>>> Can anyone help me solve this issue? >>>> > > >>>>>> >>>> > > >>>>>> thanks >>>> > > >>>>>> zhihai >>>> > > >>>>>> >>>> > > >>>>>> >>>> > > >>>>>> >>>> > > >>>>>> >>>> > > >>>>>> On Mon, May 16, 2016 at 12:22 AM, Zheng, Kai >>>> >>>> > > >>>> > > >>>>>> >>>> > > >>>>> wrote: >>>> > > >>>>> >>>> > > >>>>>> >>>> > > >>>>>> It works for me now, thanks Andrew! >>>> > > >>>>>>> >>>> > > >>>>>>> Regards, >>>> > > >>>>>>> Kai >>>> > > >>>>>>> >>>> > > >>>>>>> -----Original Message----- >>>> > > >>>>>>> From: Andrew Wang [mailto:andrew.wang@cloudera.com >>>> ] >>>> > > >>>>>>> Sent: Monday, May 16, 2016 12:14 AM >>>> > > >>>>>>> To: Zheng, Kai >>> > >>>> > > >>>>>>> Cc: common-dev@hadoop.apache.org >>>> >>>> > > >>>>>>> Subject: Re: Different JIRA permissions for HADOOP and >>>> HDFS >>>> > > >>>>>>> >>>> > > >>>>>>> I just gave you committer permissions on JIRA, try now? >>>> > > >>>>>>> >>>> > > >>>>>>> On Mon, May 16, 2016 at 12:03 AM, Zheng, Kai < >>>> > kai.zheng@intel.com > >>>> > > >>>>>>> >>>> > > >>>>>> wrote: >>>> > > >>>>>> >>>> > > >>>>>>> >>>> > > >>>>>>> I just ran into the bad situation that I committed >>>> HDFS-8449 but >>>> > > >>>>>>>> >>>> > > >>>>>>> can't >>>> > > >>>>> >>>> > > >>>>>> resolve the issue due to lacking the required permission >>>> to me. >>>> > > >>>>>>>> >>>> > > >>>>>>> Am >>>> > > >> >>>> > > >>> not >>>> > > >>>>> >>>> > > >>>>>> sure if it's caused by my setup or environment change >>>> (temporally >>>> > > >>>>>>>> working in a new time zone). Would anyone help resolve >>>> the issue >>>> > > >>>>>>>> >>>> > > >>>>>>> for >>>> > > >>>> >>>> > > >>>>> me to avoid bad state? Thanks! >>>> > > >>>>>>>> >>>> > > >>>>>>>> -----Original Message----- >>>> > > >>>>>>>> From: Zheng, Kai [mailto:kai.zheng@intel.com >>>> ] >>>> > > >>>>>>>> Sent: Sunday, May 15, 2016 3:20 PM >>>> > > >>>>>>>> To: Allen Wittenauer >>> .INVALID> >>>> > > >>>>>>>> Cc: common-dev@hadoop.apache.org >>>> >>>> > > >>>>>>>> Subject: RE: Different JIRA permissions for HADOOP and >>>> HDFS >>>> > > >>>>>>>> >>>> > > >>>>>>>> Thanks Allen for illustrating this in details. I >>>> understand. The >>>> > > >>>>>>>> >>>> > > >>>>>>> left >>>> > > >>>> >>>> > > >>>>> question is, is it intended only JIRA owner (not sure >>>> about admin >>>> > > >>>>>>>> users) can do the operations like updating a patch? >>>> > > >>>>>>>> >>>> > > >>>>>>>> Regards, >>>> > > >>>>>>>> Kai >>>> > > >>>>>>>> >>>> > > >>>>>>>> -----Original Message----- >>>> > > >>>>>>>> From: Allen Wittenauer [mailto: >>>> > allenwittenauer@yahoo.com.INVALID] >>>> > > >>>>>>>> Sent: Saturday, May 14, 2016 9:38 AM >>>> > > >>>>>>>> To: Zheng, Kai >>> > >>>> > > >>>>>>>> Cc: common-dev@hadoop.apache.org >>>> >>>> > > >>>>>>>> Subject: Re: Different JIRA permissions for HADOOP and >>>> HDFS >>>> > > >>>>>>>> >>>> > > >>>>>>>> >>>> > > >>>>>>>> On May 14, 2016, at 7:07 AM, Zheng, Kai >>>> > >>>> > > >>>>>>>>> >>>> > > >>>>>>>> wrote: >>>> > > >>>>> >>>> > > >>>>>> >>>> > > >>>>>>>>> Hi, >>>> > > >>>>>>>>> >>>> > > >>>>>>>>> Noticed this difference but not sure if it=E2=80=99s = intended. >>>> YARN is >>>> > > >>>>>>>>> similar >>>> > > >>>>>>>>> >>>> > > >>>>>>>> with HDFS. It=E2=80=99s not convenient. Any clarifying= ? >>>> > > >>>>>>>> >>>> > > >>>>>>>> >>>> > > >>>>>>>> Under JIRA, different projects (e.g., HADOOP, >>>> YARN, >>>> > > >>>>>>>> >>>> > > >>>>>>> MAPREDUCE, >>>> > > >>>>> >>>> > > >>>>>> HDFS, YETUS, HBASE, ACCUMULO, etc) may have different >>>> settings. >>>> > > >>>>>>>> >>>> > > >>>>>>> At >>>> > > >>>> >>>> > > >>>>> one point in time, all of the Hadoop subprojects were >>>> under one >>>> > > >>>>>>>> >>>> > > >>>>>>> JIRA >>>> > > >>>> >>>> > > >>>>> project (HADOOP). But then a bunch of folks decided they >>>> didn=E2=80=99t >>>> > > >>>>>>>> >>>> > > >>>>>>> want >>>> > > >>>> >>>> > > >>>>> to see the other sub projects issues so they split them >>>> up=E2=80=A6. and >>>> > > >>>>>>>> >>>> > > >>>>>>> thus >>>> > > >>>> >>>> > > >>>>> setting the stage for duplicate code and operational >>>> divergence >>>> > > >>>>>>>> >>>> > > >>>>>>> in >>>> > > >> >>>> > > >>> the >>>> > > >>>>> >>>> > > >>>>>> source. >>>> > > >>>>>>> >>>> > > >>>>>>>> >>>> > > >>>>>>>> Since people don=E2=80=99t realize or care tha= t they are >>>> > > >>>>>>>> >>>> > > >>>>>>> separate, >>>> > > >> >>>> > > >>> people will file INFRA tickets or whatever to change =E2=80= =9Ctheir >>>> > > >>>>>>>> >>>> > > >>>>>>> project=E2=80=9D >>>> > > >>>> >>>> > > >>>>> and not the rest. This leads to the JIRA projects also >>>> diverging=E2=80=A6 >>>> > > >>>>>>>> which ultimately drives those of us who actually look >>>> at the >>>> > > >>>>>>>> >>>> > > >>>>>>> project >>>> > > >>>> >>>> > > >>>>> as >>>> > > >>>>> >>>> > > >>>>>> a whole bonkers. >>>> > > >>>>>>> >>>> > > >>>>>>>> >>>> > > >>>>>>>> >>>> > > >>>> >>>> > >>>> --------------------------------------------------------------------- >>>> > > >>>> >>>> > > >>>>> To unsubscribe, e-mail: >>>> common-dev-unsubscribe@hadoop.apache.org >>>> >>>> > > >>>>>>>> For additional commands, e-mail: >>>> > > >>>>>>>> >>>> > > >>>>>>> common-dev-help@hadoop.apache.org >>>> >>>> > > >>>> >>>> > > >>>>> >>>> > > >>>>>>>> >>>> > > >>>>>>>> >>>> > > >>>>>>>> >>>> > > >>>> >>>> > >>>> --------------------------------------------------------------------- >>>> > > >>>> >>>> > > >>>>> To unsubscribe, e-mail: >>>> common-dev-unsubscribe@hadoop.apache.org >>>> >>>> > > >>>>>>>> For additional commands, e-mail: >>>> > > >>>>>>>> >>>> > > >>>>>>> common-dev-help@hadoop.apache.org >>>> >>>> > > >>>> >>>> > > >>>>> >>>> > > >>>>>>>> >>>> > > >>>>>>> >>>> > > >>>>>>> >>>> > > >>>> -------------------------------------------------------------------= -- >>>> > > >>>> >>>> > > >>>>> To unsubscribe, e-mail: >>>> common-dev-unsubscribe@hadoop.apache.org >>>> >>>> > > >>>>>>> For additional commands, e-mail: >>>> > common-dev-help@hadoop.apache.org >>>> >>>> > > >>>>>>> >>>> > > >>>>>>> >>>> > > >>>>>> >>>> > > >>>>> >>>> > > >>>> >>>> > > >>> >>>> > > >>> >>>> > > >> >>>> > > > >>>> > > >>>> > >>>> >>>> >>>> >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org >>> For additional commands, e-mail: common-dev-help@hadoop.apache.org >>> >>> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org >> For additional commands, e-mail: common-dev-help@hadoop.apache.org >> >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: yarn-dev-unsubscribe@hadoop.apache.org > For additional commands, e-mail: yarn-dev-help@hadoop.apache.org > > --001a1143f846634f0f053316d890--