You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@impala.apache.org by Jim Apple <jb...@cloudera.com> on 2017/03/13 21:24:35 UTC
Impala JIRA migration to https://issues.apache.org/jira is complete
*If you read or write Impala JIRAs, this message is for you.*
Impala's JIRA is now at https://issues.apache.org/jira/browse/IMPALA/.
Links like https://issues.cloudera.org/browse/IMPALA-3224 should now
redirect to https://issues.apache.org/jira/browse/IMPALA-3224.
Permissions on the Apache JIRA are much more strict. We have tried to make
them almost as permissive for the IMPALA project as they were on the IMPALA
project on issues.cloudera.org. If you need permissions you don't have,
please email dev@impala.apache.org.
Other than that, we don't know of any major issues at this point, however
we have found and fixed some unexpected problems so far, and others may
exist. If you find something that is impeding your work, please file a
subtask of https://issues.apache.org/jira/browse/IMPALA-5064.
We tried to translate usernames as accurately as possible. In many cases
this worked just fine. In some cases this was not possible, and you will
see the issues that you participated on as $OLDUSERNAME now list you as
$OLDUSERNAME_impala_1de3, with some random-looking hex digits after your
name. You can claim that username by resetting your password:
1. Go to https://issues.apache.org/jira/secure/ForgotLoginDetails.jspa
2. Forgot Password, enter the username that looks like
$OLDUSERNAME_impala_1ead
3. Wait for email
4. Reset password
If you have problems with that process, please follow
https://www.apache.org/dev/infra-contact and contact Apache infrastructure.
The Impala community does not administer the JIRA server.
Re: Impala JIRA migration to https://issues.apache.org/jira is complete
Posted by Joseph McDonnell <jo...@cloudera.com>.
Thanks, it is fixed for me now.
-Joe
On Tue, Mar 14, 2017 at 2:57 PM, Jim Apple <jb...@cloudera.com> wrote:
> They said they did it in the wrong place and now did it in the right place.
> If you already tried and it failed, please do so again.
>
> Also, for future issues like this, if possible, file a JIRA so we can keep
> the discussion organized and focused on the people most interested in it.
>
> On Tue, Mar 14, 2017 at 2:43 PM, Jim Apple <jb...@cloudera.com> wrote:
>
> > They said this is now done. Joe, can you try again? If it fails, can you
> > please say the username you are logged in as and the issue you wish to
> > resolve? This will help debug.
> >
> > On Tue, Mar 14, 2017 at 2:33 PM, Jim Apple <jb...@cloudera.com> wrote:
> >
> >> I am going to ask INFRA if there is any reason why the Committers group
> >> must contain only actual committers. If not, I will add contributors to
> >> that group.
> >>
> >> On Tue, Mar 14, 2017 at 2:24 PM, Bharath Vissapragada <
> >> bharathv@cloudera.com> wrote:
> >>
> >>> Yes, that looks like a limitation in the way we can define role
> mappings
> >>> in
> >>> this jira instance. Basically, there are three groups committers,
> >>> contributors and developers and looks like only the committers can
> >>> resolve
> >>> someone else's issues. Unfortunately jira doesn't let us create custom
> >>> roles to achieve a functionality like this.
> >>>
> >>> On Tue, Mar 14, 2017 at 11:27 AM, Joseph McDonnell <
> >>> joemcdonnell@cloudera.com> wrote:
> >>>
> >>> > I have some JIRAs I need to resolve, but the "Resolve Issue/Close
> >>> Issue"
> >>> > button group is not available on them. I see it on JIRAs that I filed
> >>> and
> >>> > assigned to myself but not on JIRAs filed by other developers. Is
> this
> >>> a
> >>> > known issue?
> >>> >
> >>> > Thanks,
> >>> > Joe
> >>> >
> >>> > On Tue, Mar 14, 2017 at 11:05 AM, Bharath Vissapragada <
> >>> > bharathv@cloudera.com> wrote:
> >>> >
> >>> > > Dimitris, could you check now?
> >>> > >
> >>> > > On Tue, Mar 14, 2017 at 10:35 AM, Dimitris Tsirogiannis <
> >>> > > dtsirogiannis@cloudera.com> wrote:
> >>> > >
> >>> > > > I can't seem to be able to assign a JIRA. Is there something I
> >>> need to
> >>> > do
> >>> > > > for that?
> >>> > > >
> >>> > > > Dimitris
> >>> > > >
> >>> > > > On Tue, Mar 14, 2017 at 10:23 AM, Henry Robinson <
> >>> henry@cloudera.com>
> >>> > > > wrote:
> >>> > > >
> >>> > > > > It seems like they're re-assigned to you already. I'm not sure
> >>> what
> >>> > the
> >>> > > > > role set-up looks like on the ASF JIRA, but I have permissions
> to
> >>> > make
> >>> > > a
> >>> > > > > bulk change if you'd like anything done to all your issues at
> >>> once.
> >>> > > > >
> >>> > > > > Henry
> >>> > > > >
> >>> > > > > On 14 March 2017 at 10:14, Jim Apple <jb...@cloudera.com>
> >>> wrote:
> >>> > > > >
> >>> > > > > > You might ask the admins of the server to change that
> username,
> >>> > but I
> >>> > > > > don't
> >>> > > > > > know if they are willing to provide that level of
> >>> individualized
> >>> > > > service.
> >>> > > > > >
> >>> > > > > > https://www.apache.org/dev/infra-contact
> >>> > > > > >
> >>> > > > > > On Tue, Mar 14, 2017 at 8:33 AM, Zachary Amsden <
> >>> > > zamsden@cloudera.com>
> >>> > > > > > wrote:
> >>> > > > > >
> >>> > > > > > > As one of those affected, what should I do? I already
> >>> created a
> >>> > > new
> >>> > > > > > > account as zamsden, but all of my issues are assigned to
> >>> > > > > > > zamsden_impala_ad21. Should I reassign and transfer things
> >>> over
> >>> > or
> >>> > > > am
> >>> > > > > I
> >>> > > > > > > forever doomed to be zamsden_impala_ad21?
> >>> > > > > > >
> >>> > > > > >
> >>> > > > >
> >>> > > > >
> >>> > > > >
> >>> > > > > --
> >>> > > > > Henry Robinson
> >>> > > > > Software Engineer
> >>> > > > > Cloudera
> >>> > > > > 415-994-6679
> >>> > > > >
> >>> > > >
> >>> > >
> >>> >
> >>>
> >>
> >>
> >
>
Re: Impala JIRA migration to https://issues.apache.org/jira is complete
Posted by Jim Apple <jb...@cloudera.com>.
They said they did it in the wrong place and now did it in the right place.
If you already tried and it failed, please do so again.
Also, for future issues like this, if possible, file a JIRA so we can keep
the discussion organized and focused on the people most interested in it.
On Tue, Mar 14, 2017 at 2:43 PM, Jim Apple <jb...@cloudera.com> wrote:
> They said this is now done. Joe, can you try again? If it fails, can you
> please say the username you are logged in as and the issue you wish to
> resolve? This will help debug.
>
> On Tue, Mar 14, 2017 at 2:33 PM, Jim Apple <jb...@cloudera.com> wrote:
>
>> I am going to ask INFRA if there is any reason why the Committers group
>> must contain only actual committers. If not, I will add contributors to
>> that group.
>>
>> On Tue, Mar 14, 2017 at 2:24 PM, Bharath Vissapragada <
>> bharathv@cloudera.com> wrote:
>>
>>> Yes, that looks like a limitation in the way we can define role mappings
>>> in
>>> this jira instance. Basically, there are three groups committers,
>>> contributors and developers and looks like only the committers can
>>> resolve
>>> someone else's issues. Unfortunately jira doesn't let us create custom
>>> roles to achieve a functionality like this.
>>>
>>> On Tue, Mar 14, 2017 at 11:27 AM, Joseph McDonnell <
>>> joemcdonnell@cloudera.com> wrote:
>>>
>>> > I have some JIRAs I need to resolve, but the "Resolve Issue/Close
>>> Issue"
>>> > button group is not available on them. I see it on JIRAs that I filed
>>> and
>>> > assigned to myself but not on JIRAs filed by other developers. Is this
>>> a
>>> > known issue?
>>> >
>>> > Thanks,
>>> > Joe
>>> >
>>> > On Tue, Mar 14, 2017 at 11:05 AM, Bharath Vissapragada <
>>> > bharathv@cloudera.com> wrote:
>>> >
>>> > > Dimitris, could you check now?
>>> > >
>>> > > On Tue, Mar 14, 2017 at 10:35 AM, Dimitris Tsirogiannis <
>>> > > dtsirogiannis@cloudera.com> wrote:
>>> > >
>>> > > > I can't seem to be able to assign a JIRA. Is there something I
>>> need to
>>> > do
>>> > > > for that?
>>> > > >
>>> > > > Dimitris
>>> > > >
>>> > > > On Tue, Mar 14, 2017 at 10:23 AM, Henry Robinson <
>>> henry@cloudera.com>
>>> > > > wrote:
>>> > > >
>>> > > > > It seems like they're re-assigned to you already. I'm not sure
>>> what
>>> > the
>>> > > > > role set-up looks like on the ASF JIRA, but I have permissions to
>>> > make
>>> > > a
>>> > > > > bulk change if you'd like anything done to all your issues at
>>> once.
>>> > > > >
>>> > > > > Henry
>>> > > > >
>>> > > > > On 14 March 2017 at 10:14, Jim Apple <jb...@cloudera.com>
>>> wrote:
>>> > > > >
>>> > > > > > You might ask the admins of the server to change that username,
>>> > but I
>>> > > > > don't
>>> > > > > > know if they are willing to provide that level of
>>> individualized
>>> > > > service.
>>> > > > > >
>>> > > > > > https://www.apache.org/dev/infra-contact
>>> > > > > >
>>> > > > > > On Tue, Mar 14, 2017 at 8:33 AM, Zachary Amsden <
>>> > > zamsden@cloudera.com>
>>> > > > > > wrote:
>>> > > > > >
>>> > > > > > > As one of those affected, what should I do? I already
>>> created a
>>> > > new
>>> > > > > > > account as zamsden, but all of my issues are assigned to
>>> > > > > > > zamsden_impala_ad21. Should I reassign and transfer things
>>> over
>>> > or
>>> > > > am
>>> > > > > I
>>> > > > > > > forever doomed to be zamsden_impala_ad21?
>>> > > > > > >
>>> > > > > >
>>> > > > >
>>> > > > >
>>> > > > >
>>> > > > > --
>>> > > > > Henry Robinson
>>> > > > > Software Engineer
>>> > > > > Cloudera
>>> > > > > 415-994-6679
>>> > > > >
>>> > > >
>>> > >
>>> >
>>>
>>
>>
>
Re: Impala JIRA migration to https://issues.apache.org/jira is complete
Posted by Jim Apple <jb...@cloudera.com>.
They said this is now done. Joe, can you try again? If it fails, can you
please say the username you are logged in as and the issue you wish to
resolve? This will help debug.
On Tue, Mar 14, 2017 at 2:33 PM, Jim Apple <jb...@cloudera.com> wrote:
> I am going to ask INFRA if there is any reason why the Committers group
> must contain only actual committers. If not, I will add contributors to
> that group.
>
> On Tue, Mar 14, 2017 at 2:24 PM, Bharath Vissapragada <
> bharathv@cloudera.com> wrote:
>
>> Yes, that looks like a limitation in the way we can define role mappings
>> in
>> this jira instance. Basically, there are three groups committers,
>> contributors and developers and looks like only the committers can resolve
>> someone else's issues. Unfortunately jira doesn't let us create custom
>> roles to achieve a functionality like this.
>>
>> On Tue, Mar 14, 2017 at 11:27 AM, Joseph McDonnell <
>> joemcdonnell@cloudera.com> wrote:
>>
>> > I have some JIRAs I need to resolve, but the "Resolve Issue/Close Issue"
>> > button group is not available on them. I see it on JIRAs that I filed
>> and
>> > assigned to myself but not on JIRAs filed by other developers. Is this a
>> > known issue?
>> >
>> > Thanks,
>> > Joe
>> >
>> > On Tue, Mar 14, 2017 at 11:05 AM, Bharath Vissapragada <
>> > bharathv@cloudera.com> wrote:
>> >
>> > > Dimitris, could you check now?
>> > >
>> > > On Tue, Mar 14, 2017 at 10:35 AM, Dimitris Tsirogiannis <
>> > > dtsirogiannis@cloudera.com> wrote:
>> > >
>> > > > I can't seem to be able to assign a JIRA. Is there something I need
>> to
>> > do
>> > > > for that?
>> > > >
>> > > > Dimitris
>> > > >
>> > > > On Tue, Mar 14, 2017 at 10:23 AM, Henry Robinson <
>> henry@cloudera.com>
>> > > > wrote:
>> > > >
>> > > > > It seems like they're re-assigned to you already. I'm not sure
>> what
>> > the
>> > > > > role set-up looks like on the ASF JIRA, but I have permissions to
>> > make
>> > > a
>> > > > > bulk change if you'd like anything done to all your issues at
>> once.
>> > > > >
>> > > > > Henry
>> > > > >
>> > > > > On 14 March 2017 at 10:14, Jim Apple <jb...@cloudera.com>
>> wrote:
>> > > > >
>> > > > > > You might ask the admins of the server to change that username,
>> > but I
>> > > > > don't
>> > > > > > know if they are willing to provide that level of individualized
>> > > > service.
>> > > > > >
>> > > > > > https://www.apache.org/dev/infra-contact
>> > > > > >
>> > > > > > On Tue, Mar 14, 2017 at 8:33 AM, Zachary Amsden <
>> > > zamsden@cloudera.com>
>> > > > > > wrote:
>> > > > > >
>> > > > > > > As one of those affected, what should I do? I already
>> created a
>> > > new
>> > > > > > > account as zamsden, but all of my issues are assigned to
>> > > > > > > zamsden_impala_ad21. Should I reassign and transfer things
>> over
>> > or
>> > > > am
>> > > > > I
>> > > > > > > forever doomed to be zamsden_impala_ad21?
>> > > > > > >
>> > > > > >
>> > > > >
>> > > > >
>> > > > >
>> > > > > --
>> > > > > Henry Robinson
>> > > > > Software Engineer
>> > > > > Cloudera
>> > > > > 415-994-6679
>> > > > >
>> > > >
>> > >
>> >
>>
>
>
Re: Impala JIRA migration to https://issues.apache.org/jira is complete
Posted by Jim Apple <jb...@cloudera.com>.
I am going to ask INFRA if there is any reason why the Committers group
must contain only actual committers. If not, I will add contributors to
that group.
On Tue, Mar 14, 2017 at 2:24 PM, Bharath Vissapragada <bharathv@cloudera.com
> wrote:
> Yes, that looks like a limitation in the way we can define role mappings in
> this jira instance. Basically, there are three groups committers,
> contributors and developers and looks like only the committers can resolve
> someone else's issues. Unfortunately jira doesn't let us create custom
> roles to achieve a functionality like this.
>
> On Tue, Mar 14, 2017 at 11:27 AM, Joseph McDonnell <
> joemcdonnell@cloudera.com> wrote:
>
> > I have some JIRAs I need to resolve, but the "Resolve Issue/Close Issue"
> > button group is not available on them. I see it on JIRAs that I filed and
> > assigned to myself but not on JIRAs filed by other developers. Is this a
> > known issue?
> >
> > Thanks,
> > Joe
> >
> > On Tue, Mar 14, 2017 at 11:05 AM, Bharath Vissapragada <
> > bharathv@cloudera.com> wrote:
> >
> > > Dimitris, could you check now?
> > >
> > > On Tue, Mar 14, 2017 at 10:35 AM, Dimitris Tsirogiannis <
> > > dtsirogiannis@cloudera.com> wrote:
> > >
> > > > I can't seem to be able to assign a JIRA. Is there something I need
> to
> > do
> > > > for that?
> > > >
> > > > Dimitris
> > > >
> > > > On Tue, Mar 14, 2017 at 10:23 AM, Henry Robinson <henry@cloudera.com
> >
> > > > wrote:
> > > >
> > > > > It seems like they're re-assigned to you already. I'm not sure what
> > the
> > > > > role set-up looks like on the ASF JIRA, but I have permissions to
> > make
> > > a
> > > > > bulk change if you'd like anything done to all your issues at once.
> > > > >
> > > > > Henry
> > > > >
> > > > > On 14 March 2017 at 10:14, Jim Apple <jb...@cloudera.com> wrote:
> > > > >
> > > > > > You might ask the admins of the server to change that username,
> > but I
> > > > > don't
> > > > > > know if they are willing to provide that level of individualized
> > > > service.
> > > > > >
> > > > > > https://www.apache.org/dev/infra-contact
> > > > > >
> > > > > > On Tue, Mar 14, 2017 at 8:33 AM, Zachary Amsden <
> > > zamsden@cloudera.com>
> > > > > > wrote:
> > > > > >
> > > > > > > As one of those affected, what should I do? I already created
> a
> > > new
> > > > > > > account as zamsden, but all of my issues are assigned to
> > > > > > > zamsden_impala_ad21. Should I reassign and transfer things
> over
> > or
> > > > am
> > > > > I
> > > > > > > forever doomed to be zamsden_impala_ad21?
> > > > > > >
> > > > > >
> > > > >
> > > > >
> > > > >
> > > > > --
> > > > > Henry Robinson
> > > > > Software Engineer
> > > > > Cloudera
> > > > > 415-994-6679
> > > > >
> > > >
> > >
> >
>
Re: Impala JIRA migration to https://issues.apache.org/jira is complete
Posted by Bharath Vissapragada <bh...@cloudera.com>.
Yes, that looks like a limitation in the way we can define role mappings in
this jira instance. Basically, there are three groups committers,
contributors and developers and looks like only the committers can resolve
someone else's issues. Unfortunately jira doesn't let us create custom
roles to achieve a functionality like this.
On Tue, Mar 14, 2017 at 11:27 AM, Joseph McDonnell <
joemcdonnell@cloudera.com> wrote:
> I have some JIRAs I need to resolve, but the "Resolve Issue/Close Issue"
> button group is not available on them. I see it on JIRAs that I filed and
> assigned to myself but not on JIRAs filed by other developers. Is this a
> known issue?
>
> Thanks,
> Joe
>
> On Tue, Mar 14, 2017 at 11:05 AM, Bharath Vissapragada <
> bharathv@cloudera.com> wrote:
>
> > Dimitris, could you check now?
> >
> > On Tue, Mar 14, 2017 at 10:35 AM, Dimitris Tsirogiannis <
> > dtsirogiannis@cloudera.com> wrote:
> >
> > > I can't seem to be able to assign a JIRA. Is there something I need to
> do
> > > for that?
> > >
> > > Dimitris
> > >
> > > On Tue, Mar 14, 2017 at 10:23 AM, Henry Robinson <he...@cloudera.com>
> > > wrote:
> > >
> > > > It seems like they're re-assigned to you already. I'm not sure what
> the
> > > > role set-up looks like on the ASF JIRA, but I have permissions to
> make
> > a
> > > > bulk change if you'd like anything done to all your issues at once.
> > > >
> > > > Henry
> > > >
> > > > On 14 March 2017 at 10:14, Jim Apple <jb...@cloudera.com> wrote:
> > > >
> > > > > You might ask the admins of the server to change that username,
> but I
> > > > don't
> > > > > know if they are willing to provide that level of individualized
> > > service.
> > > > >
> > > > > https://www.apache.org/dev/infra-contact
> > > > >
> > > > > On Tue, Mar 14, 2017 at 8:33 AM, Zachary Amsden <
> > zamsden@cloudera.com>
> > > > > wrote:
> > > > >
> > > > > > As one of those affected, what should I do? I already created a
> > new
> > > > > > account as zamsden, but all of my issues are assigned to
> > > > > > zamsden_impala_ad21. Should I reassign and transfer things over
> or
> > > am
> > > > I
> > > > > > forever doomed to be zamsden_impala_ad21?
> > > > > >
> > > > >
> > > >
> > > >
> > > >
> > > > --
> > > > Henry Robinson
> > > > Software Engineer
> > > > Cloudera
> > > > 415-994-6679
> > > >
> > >
> >
>
Re: Impala JIRA migration to https://issues.apache.org/jira is complete
Posted by Joseph McDonnell <jo...@cloudera.com>.
I have some JIRAs I need to resolve, but the "Resolve Issue/Close Issue"
button group is not available on them. I see it on JIRAs that I filed and
assigned to myself but not on JIRAs filed by other developers. Is this a
known issue?
Thanks,
Joe
On Tue, Mar 14, 2017 at 11:05 AM, Bharath Vissapragada <
bharathv@cloudera.com> wrote:
> Dimitris, could you check now?
>
> On Tue, Mar 14, 2017 at 10:35 AM, Dimitris Tsirogiannis <
> dtsirogiannis@cloudera.com> wrote:
>
> > I can't seem to be able to assign a JIRA. Is there something I need to do
> > for that?
> >
> > Dimitris
> >
> > On Tue, Mar 14, 2017 at 10:23 AM, Henry Robinson <he...@cloudera.com>
> > wrote:
> >
> > > It seems like they're re-assigned to you already. I'm not sure what the
> > > role set-up looks like on the ASF JIRA, but I have permissions to make
> a
> > > bulk change if you'd like anything done to all your issues at once.
> > >
> > > Henry
> > >
> > > On 14 March 2017 at 10:14, Jim Apple <jb...@cloudera.com> wrote:
> > >
> > > > You might ask the admins of the server to change that username, but I
> > > don't
> > > > know if they are willing to provide that level of individualized
> > service.
> > > >
> > > > https://www.apache.org/dev/infra-contact
> > > >
> > > > On Tue, Mar 14, 2017 at 8:33 AM, Zachary Amsden <
> zamsden@cloudera.com>
> > > > wrote:
> > > >
> > > > > As one of those affected, what should I do? I already created a
> new
> > > > > account as zamsden, but all of my issues are assigned to
> > > > > zamsden_impala_ad21. Should I reassign and transfer things over or
> > am
> > > I
> > > > > forever doomed to be zamsden_impala_ad21?
> > > > >
> > > >
> > >
> > >
> > >
> > > --
> > > Henry Robinson
> > > Software Engineer
> > > Cloudera
> > > 415-994-6679
> > >
> >
>
Re: Impala JIRA migration to https://issues.apache.org/jira is complete
Posted by Jim Apple <jb...@cloudera.com>.
You can check infra status at http://status.apache.org/. http://infra.chat
is useful if you want to watch what the infra folks are talking about among
themselves.
On Tue, Mar 14, 2017 at 11:28 AM, Dimitris Tsirogiannis <
dtsirogiannis@cloudera.com> wrote:
> Thanks Bharath, I will try again. The issue I currently have is that
> issues.apache.org is so slow to the point of being unusable.
>
> Dimitris
>
> On Tue, Mar 14, 2017 at 11:05 AM, Bharath Vissapragada <
> bharathv@cloudera.com> wrote:
>
> > Dimitris, could you check now?
> >
> > On Tue, Mar 14, 2017 at 10:35 AM, Dimitris Tsirogiannis <
> > dtsirogiannis@cloudera.com> wrote:
> >
> > > I can't seem to be able to assign a JIRA. Is there something I need to
> do
> > > for that?
> > >
> > > Dimitris
> > >
> > > On Tue, Mar 14, 2017 at 10:23 AM, Henry Robinson <he...@cloudera.com>
> > > wrote:
> > >
> > > > It seems like they're re-assigned to you already. I'm not sure what
> the
> > > > role set-up looks like on the ASF JIRA, but I have permissions to
> make
> > a
> > > > bulk change if you'd like anything done to all your issues at once.
> > > >
> > > > Henry
> > > >
> > > > On 14 March 2017 at 10:14, Jim Apple <jb...@cloudera.com> wrote:
> > > >
> > > > > You might ask the admins of the server to change that username,
> but I
> > > > don't
> > > > > know if they are willing to provide that level of individualized
> > > service.
> > > > >
> > > > > https://www.apache.org/dev/infra-contact
> > > > >
> > > > > On Tue, Mar 14, 2017 at 8:33 AM, Zachary Amsden <
> > zamsden@cloudera.com>
> > > > > wrote:
> > > > >
> > > > > > As one of those affected, what should I do? I already created a
> > new
> > > > > > account as zamsden, but all of my issues are assigned to
> > > > > > zamsden_impala_ad21. Should I reassign and transfer things over
> or
> > > am
> > > > I
> > > > > > forever doomed to be zamsden_impala_ad21?
> > > > > >
> > > > >
> > > >
> > > >
> > > >
> > > > --
> > > > Henry Robinson
> > > > Software Engineer
> > > > Cloudera
> > > > 415-994-6679
> > > >
> > >
> >
>
Re: Impala JIRA migration to https://issues.apache.org/jira is complete
Posted by Bharath Vissapragada <bh...@cloudera.com>.
Thanks for the update Dimitris. I'm noticing the slowness too sometimes and
I just retry the operations to get them working. I think we need to get
used to that :D.
On Tue, Mar 14, 2017 at 11:29 AM, Dimitris Tsirogiannis <
dtsirogiannis@cloudera.com> wrote:
> Btw, I can assign JIRAs now. Thanks
>
> Dimitris
>
> On Tue, Mar 14, 2017 at 11:28 AM, Dimitris Tsirogiannis <
> dtsirogiannis@cloudera.com> wrote:
>
> > Thanks Bharath, I will try again. The issue I currently have is that
> > issues.apache.org is so slow to the point of being unusable.
> >
> > Dimitris
> >
> > On Tue, Mar 14, 2017 at 11:05 AM, Bharath Vissapragada <
> > bharathv@cloudera.com> wrote:
> >
> >> Dimitris, could you check now?
> >>
> >> On Tue, Mar 14, 2017 at 10:35 AM, Dimitris Tsirogiannis <
> >> dtsirogiannis@cloudera.com> wrote:
> >>
> >> > I can't seem to be able to assign a JIRA. Is there something I need to
> >> do
> >> > for that?
> >> >
> >> > Dimitris
> >> >
> >> > On Tue, Mar 14, 2017 at 10:23 AM, Henry Robinson <he...@cloudera.com>
> >> > wrote:
> >> >
> >> > > It seems like they're re-assigned to you already. I'm not sure what
> >> the
> >> > > role set-up looks like on the ASF JIRA, but I have permissions to
> >> make a
> >> > > bulk change if you'd like anything done to all your issues at once.
> >> > >
> >> > > Henry
> >> > >
> >> > > On 14 March 2017 at 10:14, Jim Apple <jb...@cloudera.com> wrote:
> >> > >
> >> > > > You might ask the admins of the server to change that username,
> but
> >> I
> >> > > don't
> >> > > > know if they are willing to provide that level of individualized
> >> > service.
> >> > > >
> >> > > > https://www.apache.org/dev/infra-contact
> >> > > >
> >> > > > On Tue, Mar 14, 2017 at 8:33 AM, Zachary Amsden <
> >> zamsden@cloudera.com>
> >> > > > wrote:
> >> > > >
> >> > > > > As one of those affected, what should I do? I already created a
> >> new
> >> > > > > account as zamsden, but all of my issues are assigned to
> >> > > > > zamsden_impala_ad21. Should I reassign and transfer things over
> >> or
> >> > am
> >> > > I
> >> > > > > forever doomed to be zamsden_impala_ad21?
> >> > > > >
> >> > > >
> >> > >
> >> > >
> >> > >
> >> > > --
> >> > > Henry Robinson
> >> > > Software Engineer
> >> > > Cloudera
> >> > > 415-994-6679
> >> > >
> >> >
> >>
> >
> >
>
Re: Impala JIRA migration to https://issues.apache.org/jira is complete
Posted by Dimitris Tsirogiannis <dt...@cloudera.com>.
Btw, I can assign JIRAs now. Thanks
Dimitris
On Tue, Mar 14, 2017 at 11:28 AM, Dimitris Tsirogiannis <
dtsirogiannis@cloudera.com> wrote:
> Thanks Bharath, I will try again. The issue I currently have is that
> issues.apache.org is so slow to the point of being unusable.
>
> Dimitris
>
> On Tue, Mar 14, 2017 at 11:05 AM, Bharath Vissapragada <
> bharathv@cloudera.com> wrote:
>
>> Dimitris, could you check now?
>>
>> On Tue, Mar 14, 2017 at 10:35 AM, Dimitris Tsirogiannis <
>> dtsirogiannis@cloudera.com> wrote:
>>
>> > I can't seem to be able to assign a JIRA. Is there something I need to
>> do
>> > for that?
>> >
>> > Dimitris
>> >
>> > On Tue, Mar 14, 2017 at 10:23 AM, Henry Robinson <he...@cloudera.com>
>> > wrote:
>> >
>> > > It seems like they're re-assigned to you already. I'm not sure what
>> the
>> > > role set-up looks like on the ASF JIRA, but I have permissions to
>> make a
>> > > bulk change if you'd like anything done to all your issues at once.
>> > >
>> > > Henry
>> > >
>> > > On 14 March 2017 at 10:14, Jim Apple <jb...@cloudera.com> wrote:
>> > >
>> > > > You might ask the admins of the server to change that username, but
>> I
>> > > don't
>> > > > know if they are willing to provide that level of individualized
>> > service.
>> > > >
>> > > > https://www.apache.org/dev/infra-contact
>> > > >
>> > > > On Tue, Mar 14, 2017 at 8:33 AM, Zachary Amsden <
>> zamsden@cloudera.com>
>> > > > wrote:
>> > > >
>> > > > > As one of those affected, what should I do? I already created a
>> new
>> > > > > account as zamsden, but all of my issues are assigned to
>> > > > > zamsden_impala_ad21. Should I reassign and transfer things over
>> or
>> > am
>> > > I
>> > > > > forever doomed to be zamsden_impala_ad21?
>> > > > >
>> > > >
>> > >
>> > >
>> > >
>> > > --
>> > > Henry Robinson
>> > > Software Engineer
>> > > Cloudera
>> > > 415-994-6679
>> > >
>> >
>>
>
>
Re: Impala JIRA migration to https://issues.apache.org/jira is complete
Posted by Dimitris Tsirogiannis <dt...@cloudera.com>.
Thanks Bharath, I will try again. The issue I currently have is that
issues.apache.org is so slow to the point of being unusable.
Dimitris
On Tue, Mar 14, 2017 at 11:05 AM, Bharath Vissapragada <
bharathv@cloudera.com> wrote:
> Dimitris, could you check now?
>
> On Tue, Mar 14, 2017 at 10:35 AM, Dimitris Tsirogiannis <
> dtsirogiannis@cloudera.com> wrote:
>
> > I can't seem to be able to assign a JIRA. Is there something I need to do
> > for that?
> >
> > Dimitris
> >
> > On Tue, Mar 14, 2017 at 10:23 AM, Henry Robinson <he...@cloudera.com>
> > wrote:
> >
> > > It seems like they're re-assigned to you already. I'm not sure what the
> > > role set-up looks like on the ASF JIRA, but I have permissions to make
> a
> > > bulk change if you'd like anything done to all your issues at once.
> > >
> > > Henry
> > >
> > > On 14 March 2017 at 10:14, Jim Apple <jb...@cloudera.com> wrote:
> > >
> > > > You might ask the admins of the server to change that username, but I
> > > don't
> > > > know if they are willing to provide that level of individualized
> > service.
> > > >
> > > > https://www.apache.org/dev/infra-contact
> > > >
> > > > On Tue, Mar 14, 2017 at 8:33 AM, Zachary Amsden <
> zamsden@cloudera.com>
> > > > wrote:
> > > >
> > > > > As one of those affected, what should I do? I already created a
> new
> > > > > account as zamsden, but all of my issues are assigned to
> > > > > zamsden_impala_ad21. Should I reassign and transfer things over or
> > am
> > > I
> > > > > forever doomed to be zamsden_impala_ad21?
> > > > >
> > > >
> > >
> > >
> > >
> > > --
> > > Henry Robinson
> > > Software Engineer
> > > Cloudera
> > > 415-994-6679
> > >
> >
>
Re: Impala JIRA migration to https://issues.apache.org/jira is complete
Posted by Bharath Vissapragada <bh...@cloudera.com>.
Dimitris, could you check now?
On Tue, Mar 14, 2017 at 10:35 AM, Dimitris Tsirogiannis <
dtsirogiannis@cloudera.com> wrote:
> I can't seem to be able to assign a JIRA. Is there something I need to do
> for that?
>
> Dimitris
>
> On Tue, Mar 14, 2017 at 10:23 AM, Henry Robinson <he...@cloudera.com>
> wrote:
>
> > It seems like they're re-assigned to you already. I'm not sure what the
> > role set-up looks like on the ASF JIRA, but I have permissions to make a
> > bulk change if you'd like anything done to all your issues at once.
> >
> > Henry
> >
> > On 14 March 2017 at 10:14, Jim Apple <jb...@cloudera.com> wrote:
> >
> > > You might ask the admins of the server to change that username, but I
> > don't
> > > know if they are willing to provide that level of individualized
> service.
> > >
> > > https://www.apache.org/dev/infra-contact
> > >
> > > On Tue, Mar 14, 2017 at 8:33 AM, Zachary Amsden <za...@cloudera.com>
> > > wrote:
> > >
> > > > As one of those affected, what should I do? I already created a new
> > > > account as zamsden, but all of my issues are assigned to
> > > > zamsden_impala_ad21. Should I reassign and transfer things over or
> am
> > I
> > > > forever doomed to be zamsden_impala_ad21?
> > > >
> > >
> >
> >
> >
> > --
> > Henry Robinson
> > Software Engineer
> > Cloudera
> > 415-994-6679
> >
>
Re: Impala JIRA migration to https://issues.apache.org/jira is complete
Posted by Dimitris Tsirogiannis <dt...@cloudera.com>.
I can't seem to be able to assign a JIRA. Is there something I need to do
for that?
Dimitris
On Tue, Mar 14, 2017 at 10:23 AM, Henry Robinson <he...@cloudera.com> wrote:
> It seems like they're re-assigned to you already. I'm not sure what the
> role set-up looks like on the ASF JIRA, but I have permissions to make a
> bulk change if you'd like anything done to all your issues at once.
>
> Henry
>
> On 14 March 2017 at 10:14, Jim Apple <jb...@cloudera.com> wrote:
>
> > You might ask the admins of the server to change that username, but I
> don't
> > know if they are willing to provide that level of individualized service.
> >
> > https://www.apache.org/dev/infra-contact
> >
> > On Tue, Mar 14, 2017 at 8:33 AM, Zachary Amsden <za...@cloudera.com>
> > wrote:
> >
> > > As one of those affected, what should I do? I already created a new
> > > account as zamsden, but all of my issues are assigned to
> > > zamsden_impala_ad21. Should I reassign and transfer things over or am
> I
> > > forever doomed to be zamsden_impala_ad21?
> > >
> >
>
>
>
> --
> Henry Robinson
> Software Engineer
> Cloudera
> 415-994-6679
>
Re: Impala JIRA migration to https://issues.apache.org/jira is complete
Posted by Bharath Vissapragada <bh...@cloudera.com>.
I did this bulk change and re-assigned all of Zach's issues to his correct
id.
On Tue, Mar 14, 2017 at 10:23 AM, Henry Robinson <he...@cloudera.com> wrote:
> It seems like they're re-assigned to you already. I'm not sure what the
> role set-up looks like on the ASF JIRA, but I have permissions to make a
> bulk change if you'd like anything done to all your issues at once.
>
> Henry
>
> On 14 March 2017 at 10:14, Jim Apple <jb...@cloudera.com> wrote:
>
> > You might ask the admins of the server to change that username, but I
> don't
> > know if they are willing to provide that level of individualized service.
> >
> > https://www.apache.org/dev/infra-contact
> >
> > On Tue, Mar 14, 2017 at 8:33 AM, Zachary Amsden <za...@cloudera.com>
> > wrote:
> >
> > > As one of those affected, what should I do? I already created a new
> > > account as zamsden, but all of my issues are assigned to
> > > zamsden_impala_ad21. Should I reassign and transfer things over or am
> I
> > > forever doomed to be zamsden_impala_ad21?
> > >
> >
>
>
>
> --
> Henry Robinson
> Software Engineer
> Cloudera
> 415-994-6679
>
Re: Impala JIRA migration to https://issues.apache.org/jira is complete
Posted by Henry Robinson <he...@cloudera.com>.
It seems like they're re-assigned to you already. I'm not sure what the
role set-up looks like on the ASF JIRA, but I have permissions to make a
bulk change if you'd like anything done to all your issues at once.
Henry
On 14 March 2017 at 10:14, Jim Apple <jb...@cloudera.com> wrote:
> You might ask the admins of the server to change that username, but I don't
> know if they are willing to provide that level of individualized service.
>
> https://www.apache.org/dev/infra-contact
>
> On Tue, Mar 14, 2017 at 8:33 AM, Zachary Amsden <za...@cloudera.com>
> wrote:
>
> > As one of those affected, what should I do? I already created a new
> > account as zamsden, but all of my issues are assigned to
> > zamsden_impala_ad21. Should I reassign and transfer things over or am I
> > forever doomed to be zamsden_impala_ad21?
> >
>
--
Henry Robinson
Software Engineer
Cloudera
415-994-6679
Re: Impala JIRA migration to https://issues.apache.org/jira is complete
Posted by Jim Apple <jb...@cloudera.com>.
You might ask the admins of the server to change that username, but I don't
know if they are willing to provide that level of individualized service.
https://www.apache.org/dev/infra-contact
On Tue, Mar 14, 2017 at 8:33 AM, Zachary Amsden <za...@cloudera.com>
wrote:
> As one of those affected, what should I do? I already created a new
> account as zamsden, but all of my issues are assigned to
> zamsden_impala_ad21. Should I reassign and transfer things over or am I
> forever doomed to be zamsden_impala_ad21?
>
Re: Impala JIRA migration to https://issues.apache.org/jira is complete
Posted by Zachary Amsden <za...@cloudera.com>.
As one of those affected, what should I do? I already created a new
account as zamsden, but all of my issues are assigned to
zamsden_impala_ad21. Should I reassign and transfer things over or am I
forever doomed to be zamsden_impala_ad21?
Thanks,
- Zach
On Mon, Mar 13, 2017 at 2:24 PM, Jim Apple <jb...@cloudera.com> wrote:
> *If you read or write Impala JIRAs, this message is for you.*
>
> Impala's JIRA is now at https://issues.apache.org/jira/browse/IMPALA/.
> Links like https://issues.cloudera.org/browse/IMPALA-3224 should now
> redirect to https://issues.apache.org/jira/browse/IMPALA-3224.
>
> Permissions on the Apache JIRA are much more strict. We have tried to make
> them almost as permissive for the IMPALA project as they were on the IMPALA
> project on issues.cloudera.org. If you need permissions you don't have,
> please email dev@impala.apache.org.
>
> Other than that, we don't know of any major issues at this point, however
> we have found and fixed some unexpected problems so far, and others may
> exist. If you find something that is impeding your work, please file a
> subtask of https://issues.apache.org/jira/browse/IMPALA-5064.
>
> We tried to translate usernames as accurately as possible. In many cases
> this worked just fine. In some cases this was not possible, and you will
> see the issues that you participated on as $OLDUSERNAME now list you as
> $OLDUSERNAME_impala_1de3, with some random-looking hex digits after your
> name. You can claim that username by resetting your password:
>
> 1. Go to https://issues.apache.org/jira/secure/ForgotLoginDetails.jspa
> 2. Forgot Password, enter the username that looks like
> $OLDUSERNAME_impala_1ead
> 3. Wait for email
> 4. Reset password
>
> If you have problems with that process, please follow
> https://www.apache.org/dev/infra-contact and contact Apache
> infrastructure. The Impala community does not administer the JIRA server.
>
Re: Impala JIRA migration to https://issues.apache.org/jira is complete
Posted by Michael Brown <mi...@cloudera.com>.
I expect such redirection to be a little difficult to configure. But it
seems like the same (or similar) JQL should work on issues.apache.org For
example:
https://issues.apache.org/jira/issues/?jql=type%20%3D%20bug%20and%20project%20%3D%20IMPALA%20AND%20resolution%20%3D%20fixed%20AND%20affectedVersion%20!%3D%20%22Impala%202.8.0%22%20AND%20fixVersion%20%3D%20%22Impala%202.8.0%22%20and%20not%20labels%20%3D%20broken-build%20order%20by%20priority%20desc
On Tue, Mar 21, 2017 at 12:47 PM, John Russell <jr...@cloudera.com>
wrote:
> Just confirming: if I have a JIRA report URL, for example
>
> https://issues.cloudera.org/issues/?jql=type%20%3D%20bug%
> 20and%20project%20%3D%20IMPALA%20AND%20resolution%20%3D%20fixed%20AND%
> 20affectedVersion%20!%3D%20%22Impala%202.8.0%22%20AND%
> 20fixVersion%20%3D%20%22Impala%202.8.0%22%20and%
> 20not%20labels%20%3D%20broken-build%20order%20by%20priority%20desc
>
> should I expect that to redirect over to issues.apache.org also?
> Currently such a report stays on issues.cloudera.org.
>
> There are a bunch of such report links in the Impala release notes.
>
> Thanks,
> John
>
> > On Mar 13, 2017, at 2:24 PM, Jim Apple <jb...@cloudera.com> wrote:
> >
> > If you read or write Impala JIRAs, this message is for you.
> >
> > Impala's JIRA is now at https://issues.apache.org/jira/browse/IMPALA/.
> Links like https://issues.cloudera.org/browse/IMPALA-3224 should now
> redirect to https://issues.apache.org/jira/browse/IMPALA-3224.
> >
> > Permissions on the Apache JIRA are much more strict. We have tried to
> make them almost as permissive for the IMPALA project as they were on the
> IMPALA project on issues.cloudera.org. If you need permissions you don't
> have, please email dev@impala.apache.org.
> >
> > Other than that, we don't know of any major issues at this point,
> however we have found and fixed some unexpected problems so far, and others
> may exist. If you find something that is impeding your work, please file a
> subtask of https://issues.apache.org/jira/browse/IMPALA-5064.
> >
> > We tried to translate usernames as accurately as possible. In many cases
> this worked just fine. In some cases this was not possible, and you will
> see the issues that you participated on as $OLDUSERNAME now list you as
> $OLDUSERNAME_impala_1de3, with some random-looking hex digits after your
> name. You can claim that username by resetting your password:
> >
> > 1. Go to https://issues.apache.org/jira/secure/ForgotLoginDetails.jspa
> > 2. Forgot Password, enter the username that looks like
> $OLDUSERNAME_impala_1ead
> > 3. Wait for email
> > 4. Reset password
> >
> > If you have problems with that process, please follow
> https://www.apache.org/dev/infra-contact and contact Apache
> infrastructure. The Impala community does not administer the JIRA server.
>
>
Re: Impala JIRA migration to https://issues.apache.org/jira is complete
Posted by John Russell <jr...@cloudera.com>.
Just confirming: if I have a JIRA report URL, for example
https://issues.cloudera.org/issues/?jql=type%20%3D%20bug%20and%20project%20%3D%20IMPALA%20AND%20resolution%20%3D%20fixed%20AND%20affectedVersion%20!%3D%20%22Impala%202.8.0%22%20AND%20fixVersion%20%3D%20%22Impala%202.8.0%22%20and%20not%20labels%20%3D%20broken-build%20order%20by%20priority%20desc
should I expect that to redirect over to issues.apache.org also? Currently such a report stays on issues.cloudera.org.
There are a bunch of such report links in the Impala release notes.
Thanks,
John
> On Mar 13, 2017, at 2:24 PM, Jim Apple <jb...@cloudera.com> wrote:
>
> If you read or write Impala JIRAs, this message is for you.
>
> Impala's JIRA is now at https://issues.apache.org/jira/browse/IMPALA/. Links like https://issues.cloudera.org/browse/IMPALA-3224 should now redirect to https://issues.apache.org/jira/browse/IMPALA-3224.
>
> Permissions on the Apache JIRA are much more strict. We have tried to make them almost as permissive for the IMPALA project as they were on the IMPALA project on issues.cloudera.org. If you need permissions you don't have, please email dev@impala.apache.org.
>
> Other than that, we don't know of any major issues at this point, however we have found and fixed some unexpected problems so far, and others may exist. If you find something that is impeding your work, please file a subtask of https://issues.apache.org/jira/browse/IMPALA-5064.
>
> We tried to translate usernames as accurately as possible. In many cases this worked just fine. In some cases this was not possible, and you will see the issues that you participated on as $OLDUSERNAME now list you as $OLDUSERNAME_impala_1de3, with some random-looking hex digits after your name. You can claim that username by resetting your password:
>
> 1. Go to https://issues.apache.org/jira/secure/ForgotLoginDetails.jspa
> 2. Forgot Password, enter the username that looks like $OLDUSERNAME_impala_1ead
> 3. Wait for email
> 4. Reset password
>
> If you have problems with that process, please follow https://www.apache.org/dev/infra-contact and contact Apache infrastructure. The Impala community does not administer the JIRA server.