You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-dev@hadoop.apache.org by Alan Burlison <Al...@oracle.com> on 2015/05/27 17:47:29 UTC
JIRA admin question: Moving a bug from Hadoop to YARN
HADOOP-11952
Native compilation on Solaris fails on Yarn due to use of FTS
is actually a YARN bug, not a Hadoop one and should be moved under the
top-level Solaris/YARN Jira:
YARN-3719 Improve Solaris support in YARN
Is that possible or do I have to close the current bug and open a fresh
one against YARN, copying everything across manually?
Thanks,
--
Alan Burlison
--
Re: JIRA admin question: Moving a bug from Hadoop to YARN
Posted by Vinod Kumar Vavilapalli <vi...@hortonworks.com>.
It actually works exactly the way you expect it to. It's just that each JIRA project needs to add a contributor only the first time he/she starts contributing (aka 'the project doesn't know who you are yet'). After that, you are free to assign tickets to yourselves.
Seems like Ravi already added you as a contributor. Contribute away!
+Vinod
On May 27, 2015, at 12:20 PM, Alan Burlison <Al...@oracle.com> wrote:
> On 27/05/2015 18:33, Ted Yu wrote:
>
>> My understanding is that once you attach patch to YARN-3724, a YARN
>> committer would assign the issue to you.
>
> Hmm, that's different to how HADOOP-XXXX JIRAs work, there you can assign a bug to yourself. Having to submit a patch first before a bug is assigned to you seems like it's going to risk multiple people working on the same bug.
>
> --
> Alan Burlison
> --
Re: JIRA admin question: Moving a bug from Hadoop to YARN
Posted by Ravi Prakash <ra...@ymail.com>.
Sorry. Deja-vu. I AM an admin. I've added your gmail account as a
contributor Alan!
On 05/27/15 12:41, Ravi Prakash wrote:
> A JIRA admin needs to add you as a contributor.
>
> Could I please be added to YARN as an admin?
>
> Thanks
> Ravi
>
> On 05/27/15 12:20, Alan Burlison wrote:
>> On 27/05/2015 18:33, Ted Yu wrote:
>>
>>> My understanding is that once you attach patch to YARN-3724, a YARN
>>> committer would assign the issue to you.
>>
>> Hmm, that's different to how HADOOP-XXXX JIRAs work, there you can
>> assign a bug to yourself. Having to submit a patch first before a bug
>> is assigned to you seems like it's going to risk multiple people
>> working on the same bug.
>>
>
Re: JIRA admin question: Moving a bug from Hadoop to YARN
Posted by Ravi Prakash <ra...@ymail.com>.
A JIRA admin needs to add you as a contributor.
Could I please be added to YARN as an admin?
Thanks
Ravi
On 05/27/15 12:20, Alan Burlison wrote:
> On 27/05/2015 18:33, Ted Yu wrote:
>
>> My understanding is that once you attach patch to YARN-3724, a YARN
>> committer would assign the issue to you.
>
> Hmm, that's different to how HADOOP-XXXX JIRAs work, there you can
> assign a bug to yourself. Having to submit a patch first before a bug
> is assigned to you seems like it's going to risk multiple people
> working on the same bug.
>
Re: JIRA admin question: Moving a bug from Hadoop to YARN
Posted by Alan Burlison <Al...@oracle.com>.
On 27/05/2015 18:33, Ted Yu wrote:
> My understanding is that once you attach patch to YARN-3724, a YARN
> committer would assign the issue to you.
Hmm, that's different to how HADOOP-XXXX JIRAs work, there you can
assign a bug to yourself. Having to submit a patch first before a bug is
assigned to you seems like it's going to risk multiple people working on
the same bug.
--
Alan Burlison
--
Re: JIRA admin question: Moving a bug from Hadoop to YARN
Posted by Ted Yu <yu...@gmail.com>.
Alan:
My understanding is that once you attach patch to YARN-3724, a YARN
committer would assign the issue to you.
On Wed, May 27, 2015 at 9:54 AM, Alan Burlison <Al...@oracle.com>
wrote:
> On 27/05/2015 16:56, Sean Busbey wrote:
>
> you might have to do things in two steps
>>
>> * move from HADOOP tracker to YARN tracker
>> * convert from YARN jira to subtask of YARN-3719
>>
>
> I had to do it in 3 steps, but you gave me the clues I needed, thanks :-)
>
> 1. Convert to a HADOOP issue
> 2. Move from Hadoop to YARN
> 3. Convert to a YARN sub-task
>
> However I don't seem to be able to assign it (YARN-3724) to myself...
>
> --
> Alan Burlison
> --
>
Re: JIRA admin question: Moving a bug from Hadoop to YARN
Posted by Alan Burlison <Al...@oracle.com>.
On 27/05/2015 16:56, Sean Busbey wrote:
> you might have to do things in two steps
>
> * move from HADOOP tracker to YARN tracker
> * convert from YARN jira to subtask of YARN-3719
I had to do it in 3 steps, but you gave me the clues I needed, thanks :-)
1. Convert to a HADOOP issue
2. Move from Hadoop to YARN
3. Convert to a YARN sub-task
However I don't seem to be able to assign it (YARN-3724) to myself...
--
Alan Burlison
--
Re: JIRA admin question: Moving a bug from Hadoop to YARN
Posted by Alan Burlison <Al...@oracle.com>.
On 27/05/2015 16:56, Sean Busbey wrote:
> you might have to do things in two steps
>
> * move from HADOOP tracker to YARN tracker
> * convert from YARN jira to subtask of YARN-3719
I had to do it in 3 steps, but you gave me the clues I needed, thanks :-)
1. Convert to a HADOOP issue
2. Move from Hadoop to YARN
3. Convert to a YARN sub-task
However I don't seem to be able to assign it (YARN-3724) to myself...
--
Alan Burlison
--
Re: JIRA admin question: Moving a bug from Hadoop to YARN
Posted by Sean Busbey <bu...@cloudera.com>.
you might have to do things in two steps
* move from HADOOP tracker to YARN tracker
* convert from YARN jira to subtask of YARN-3719
On Wed, May 27, 2015 at 10:52 AM, Ted Yu <yu...@gmail.com> wrote:
> When you click on More button, you should see an action called Move.
>
> You can move the existing JIRA.
>
> FYI
>
> On Wed, May 27, 2015 at 8:47 AM, Alan Burlison <Al...@oracle.com>
> wrote:
>
> > HADOOP-11952
> > Native compilation on Solaris fails on Yarn due to use of FTS
> >
> > is actually a YARN bug, not a Hadoop one and should be moved under the
> > top-level Solaris/YARN Jira:
> >
> > YARN-3719 Improve Solaris support in YARN
> >
> > Is that possible or do I have to close the current bug and open a fresh
> > one against YARN, copying everything across manually?
> >
> > Thanks,
> >
> > --
> > Alan Burlison
> > --
> >
>
--
Sean
Re: JIRA admin question: Moving a bug from Hadoop to YARN
Posted by Sean Busbey <bu...@cloudera.com>.
you might have to do things in two steps
* move from HADOOP tracker to YARN tracker
* convert from YARN jira to subtask of YARN-3719
On Wed, May 27, 2015 at 10:52 AM, Ted Yu <yu...@gmail.com> wrote:
> When you click on More button, you should see an action called Move.
>
> You can move the existing JIRA.
>
> FYI
>
> On Wed, May 27, 2015 at 8:47 AM, Alan Burlison <Al...@oracle.com>
> wrote:
>
> > HADOOP-11952
> > Native compilation on Solaris fails on Yarn due to use of FTS
> >
> > is actually a YARN bug, not a Hadoop one and should be moved under the
> > top-level Solaris/YARN Jira:
> >
> > YARN-3719 Improve Solaris support in YARN
> >
> > Is that possible or do I have to close the current bug and open a fresh
> > one against YARN, copying everything across manually?
> >
> > Thanks,
> >
> > --
> > Alan Burlison
> > --
> >
>
--
Sean
Re: JIRA admin question: Moving a bug from Hadoop to YARN
Posted by Ted Yu <yu...@gmail.com>.
When you click on More button, you should see an action called Move.
You can move the existing JIRA.
FYI
On Wed, May 27, 2015 at 8:47 AM, Alan Burlison <Al...@oracle.com>
wrote:
> HADOOP-11952
> Native compilation on Solaris fails on Yarn due to use of FTS
>
> is actually a YARN bug, not a Hadoop one and should be moved under the
> top-level Solaris/YARN Jira:
>
> YARN-3719 Improve Solaris support in YARN
>
> Is that possible or do I have to close the current bug and open a fresh
> one against YARN, copying everything across manually?
>
> Thanks,
>
> --
> Alan Burlison
> --
>
Re: JIRA admin question: Moving a bug from Hadoop to YARN
Posted by Ted Yu <yu...@gmail.com>.
When you click on More button, you should see an action called Move.
You can move the existing JIRA.
FYI
On Wed, May 27, 2015 at 8:47 AM, Alan Burlison <Al...@oracle.com>
wrote:
> HADOOP-11952
> Native compilation on Solaris fails on Yarn due to use of FTS
>
> is actually a YARN bug, not a Hadoop one and should be moved under the
> top-level Solaris/YARN Jira:
>
> YARN-3719 Improve Solaris support in YARN
>
> Is that possible or do I have to close the current bug and open a fresh
> one against YARN, copying everything across manually?
>
> Thanks,
>
> --
> Alan Burlison
> --
>