hadoop-yarn-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From larry mccay <lmc...@apache.org>
Subject Re: Different JIRA permissions for HADOOP and HDFS
Date Mon, 16 May 2016 12:33:44 GMT
Likewise, I've found that I am unable to set fix version, etc on a JIRA
that I committed and resolved.

On Mon, May 16, 2016 at 8:29 AM, Junping Du <jdu@hortonworks.com> wrote:

> Zhihai, I just set you with committer permissions on MAPREDUCE JIRA. Would
> you try if the JIRA assignment works now? I cannot help on 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 <asuresh@apache.org>
> 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
> Subject: Re: Different JIRA permissions for HADOOP and HDFS
>
> 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 <zhihai@uber.com> 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 anything change
> recently?
> > Can anyone help me solve this issue?
> >
> > thanks
> > zhihai
> >
> >
> >
> >
> > On Mon, May 16, 2016 at 12:22 AM, Zheng, Kai <kai.zheng@intel.com>
> 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 <kai.zheng@intel.com>
> > > 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 <allenwittenauer@yahoo.com.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 <kai.zheng@intel.com>
> > > > 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 <kai.zheng@intel.com>
> wrote:
> > > > >
> > > > > Hi,
> > > > >
> > > > > Noticed this difference but not sure if it’s intended. YARN is
> > > > > similar
> > > > with HDFS. It’s 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’t want
> > > > to see the other sub projects issues so they split them up…. and thus
> > > > setting the stage for duplicate code and operational divergence in
> the
> > > source.
> > > >
> > > >         Since people don’t realize or care that they are separate,
> > > > people will file INFRA tickets or whatever to change “their project”
> > > > and not the rest. This leads to the JIRA projects also diverging…
> > > > 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
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message