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 <[email protected]> Sent: Monday, May 16, 2016 9:42 AM To: Zhihai Xu Cc: Zheng, Kai; Andrew Wang; [email protected]; [email protected] 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 <[email protected]> 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 <[email protected]> wrote: > > > It works for me now, thanks Andrew! > > > > Regards, > > Kai > > > > -----Original Message----- > > From: Andrew Wang [mailto:[email protected]] > > Sent: Monday, May 16, 2016 12:14 AM > > To: Zheng, Kai <[email protected]> > > Cc: [email protected] > > 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 <[email protected]> > 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:[email protected]] > > > Sent: Sunday, May 15, 2016 3:20 PM > > > To: Allen Wittenauer <[email protected]> > > > Cc: [email protected] > > > 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:[email protected]] > > > Sent: Saturday, May 14, 2016 9:38 AM > > > To: Zheng, Kai <[email protected]> > > > Cc: [email protected] > > > Subject: Re: Different JIRA permissions for HADOOP and HDFS > > > > > > > > > > On May 14, 2016, at 7:07 AM, Zheng, Kai <[email protected]> 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: [email protected] > > > For additional commands, e-mail: [email protected] > > > > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: [email protected] > > > For additional commands, e-mail: [email protected] > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [email protected] > > For additional commands, e-mail: [email protected] > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
