You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hive.apache.org by Lefty Leverenz <le...@gmail.com> on 2015/02/26 22:05:25 UTC
Not getting some JIRA resolution messages
Is it just me, or has JIRA email been flaky since the issues mailing list
went into effect?
For example, although I got a commit message for HIVE-9731
<https://issues.apache.org/jira/browse/HIVE-9731> on the commits@hive
mailing list, I didn't get either the change of Resolution or the comment
about the commit -- not on dev@hive nor on issues@hive. However I did get
two subsequent messages on issues@hive when I added a TODOC1.2 label and
doc comment.
Another example: for HIVE-9509
<https://issues.apache.org/jira/browse/HIVE-9509> I got the commit comment
and Fix Version change for branch-1.0.1 on the issues@hive list but not the
prior commit comment and Resolved - Fix Version for 1.2.0.
Does anyone else have this problem?
-- Lefty
Re: Not getting some JIRA resolution messages
Posted by Lefty Leverenz <le...@gmail.com>.
Changing the status on INFRA-9221
<https://issues.apache.org/jira/browse/INFRA-9221> elicited a response from
Gavin <https://issues.apache.org/jira/secure/ViewProfile.jspa?name=ipv6guru>
:
You'll have to bear with us whilst we work out the problem.
>
> Please do keep updating us with missing mails.
>
-- Lefty
On Wed, Apr 8, 2015 at 7:06 PM, Sergey Shelukhin <se...@hortonworks.com>
wrote:
> Last time I checked that channel was changed to invite-only.
>
> From: Alan Gates <al...@gmail.com>
> Reply-To: "dev@hive.apache.org" <de...@hive.apache.org>
> Date: Wednesday, April 8, 2015 at 13:36
> To: "dev@hive.apache.org" <de...@hive.apache.org>
> Subject: Re: Not getting some JIRA resolution messages
>
> I have found the best way to get infra's attention is to hop on the IRC
> #asfinfra and ping them about the JIRA.
>
> Alan.
>
> Lefty Leverenz <le...@gmail.com>
> April 8, 2015 at 11:23
> The problem continues.
>
> I posted a few more examples on INFRA-9221
> <https://issues.apache.org/jira/browse/INFRA-9221>
> <https://issues.apache.org/jira/browse/INFRA-9221> of issues with either
> complete or incomplete messages in the issues@hive mailing list. Commits
> to trunk seem to be the main problem, while branch commits usually have
> complete records. But both have exceptions.
>
> I've changed the status of INFRA-9221
> <https://issues.apache.org/jira/browse/INFRA-9221>
> <https://issues.apache.org/jira/browse/INFRA-9221> from waiting for user
> to
> waiting for infra. Perhaps that was needed to get their attention. But I
> didn't set a review date, not knowing what's appropriate.
>
> Should I bump the priority to critical? Hive's archives are incomplete!
>
>
> -- Lefty
>
>
> Szehon Ho <sz...@cloudera.com>
> April 3, 2015 at 18:22
> Yea I added some for what its worth, +1 for bumping it if it helps as
> its
> quite annoying.
>
> Thanks
> Szehon
>
> On Fri, Apr 3, 2015 at 2:00 PM, Lefty Leverenz <le...@gmail.com>
> <le...@gmail.com>
>
> Lefty Leverenz <le...@gmail.com>
> April 3, 2015 at 14:00
> Thanks Szehon, if you could add some examples on INFRA-9221
> <https://issues.apache.org/jira/browse/INFRA-9221>
> <https://issues.apache.org/jira/browse/INFRA-9221> then maybe we'd see
> some
> action.
>
> Should we bump the priority too? It seemed a small matter at first, but
> the Apache way requires complete archives and we haven't had that for
> several weeks.
>
> -- Lefty
>
>
> Szehon Ho <sz...@cloudera.com>
> April 3, 2015 at 11:51
> Hi Lefty
>
> I am also seeing this, whenever I resolve the JIRA after commit to trunk, I
> never get the email, and probably the contributor doesn't get the email
> either.
>
> Did you find any resolution to this (is it going to different mail list)?
> If not I can add my examples tool.
>
> Thanks
> Szehon
>
> On Fri, Mar 27, 2015 at 3:20 PM, Lefty Leverenz <le...@gmail.com>
> <le...@gmail.com>
>
> Lefty Leverenz <le...@gmail.com>
> March 27, 2015 at 15:20
> This is still a problem. I'm working around it but the archives are
> incomplete, and that's not good.
>
> I updated INFRA-9221 <https://issues.apache.org/jira/browse/INFRA-9221> with
> a few more examples. Can someone corroborate please (so INFRA doesn't
> think I'm a nut-case)?
>
> Thanks.
>
> -- Lefty
>
>
>
Re: Not getting some JIRA resolution messages
Posted by Sergey Shelukhin <se...@hortonworks.com>.
Last time I checked that channel was changed to invite-only.
From: Alan Gates <al...@gmail.com>>
Reply-To: "dev@hive.apache.org<ma...@hive.apache.org>" <de...@hive.apache.org>>
Date: Wednesday, April 8, 2015 at 13:36
To: "dev@hive.apache.org<ma...@hive.apache.org>" <de...@hive.apache.org>>
Subject: Re: Not getting some JIRA resolution messages
I have found the best way to get infra's attention is to hop on the IRC #asfinfra and ping them about the JIRA.
Alan.
[cid:part1.05070506.04050703@gmail.com]
Lefty Leverenz<ma...@gmail.com>
April 8, 2015 at 11:23
The problem continues.
I posted a few more examples on INFRA-9221
<https://issues.apache.org/jira/browse/INFRA-9221><https://issues.apache.org/jira/browse/INFRA-9221> of issues with either
complete or incomplete messages in the issues@hive mailing list. Commits
to trunk seem to be the main problem, while branch commits usually have
complete records. But both have exceptions.
I've changed the status of INFRA-9221
<https://issues.apache.org/jira/browse/INFRA-9221><https://issues.apache.org/jira/browse/INFRA-9221> from waiting for user to
waiting for infra. Perhaps that was needed to get their attention. But I
didn't set a review date, not knowing what's appropriate.
Should I bump the priority to critical? Hive's archives are incomplete!
-- Lefty
[cid:part1.05070506.04050703@gmail.com]
Szehon Ho<ma...@cloudera.com>
April 3, 2015 at 18:22
Yea I added some for what its worth, +1 for bumping it if it helps as its
quite annoying.
Thanks
Szehon
On Fri, Apr 3, 2015 at 2:00 PM, Lefty Leverenz <le...@gmail.com>
[cid:part1.05070506.04050703@gmail.com]
Lefty Leverenz<ma...@gmail.com>
April 3, 2015 at 14:00
Thanks Szehon, if you could add some examples on INFRA-9221
<https://issues.apache.org/jira/browse/INFRA-9221><https://issues.apache.org/jira/browse/INFRA-9221> then maybe we'd see some
action.
Should we bump the priority too? It seemed a small matter at first, but
the Apache way requires complete archives and we haven't had that for
several weeks.
-- Lefty
[cid:part1.05070506.04050703@gmail.com]
Szehon Ho<ma...@cloudera.com>
April 3, 2015 at 11:51
Hi Lefty
I am also seeing this, whenever I resolve the JIRA after commit to trunk, I
never get the email, and probably the contributor doesn't get the email
either.
Did you find any resolution to this (is it going to different mail list)?
If not I can add my examples tool.
Thanks
Szehon
On Fri, Mar 27, 2015 at 3:20 PM, Lefty Leverenz <le...@gmail.com>
[cid:part1.05070506.04050703@gmail.com]
Lefty Leverenz<ma...@gmail.com>
March 27, 2015 at 15:20
This is still a problem. I'm working around it but the archives are incomplete, and that's not good.
I updated INFRA-9221<https://issues.apache.org/jira/browse/INFRA-9221> with a few more examples. Can someone corroborate please (so INFRA doesn't think I'm a nut-case)?
Thanks.
-- Lefty
Re: Not getting some JIRA resolution messages
Posted by Alan Gates <al...@gmail.com>.
I have found the best way to get infra's attention is to hop on the IRC
#asfinfra and ping them about the JIRA.
Alan.
> Lefty Leverenz <ma...@gmail.com>
> April 8, 2015 at 11:23
> The problem continues.
>
> I posted a few more examples on INFRA-9221
> <https://issues.apache.org/jira/browse/INFRA-9221> of issues with either
> complete or incomplete messages in the issues@hive mailing list. Commits
> to trunk seem to be the main problem, while branch commits usually have
> complete records. But both have exceptions.
>
> I've changed the status of INFRA-9221
> <https://issues.apache.org/jira/browse/INFRA-9221> from waiting for
> user to
> waiting for infra. Perhaps that was needed to get their attention. But I
> didn't set a review date, not knowing what's appropriate.
>
> Should I bump the priority to critical? Hive's archives are incomplete!
>
>
> -- Lefty
>
>
> Szehon Ho <ma...@cloudera.com>
> April 3, 2015 at 18:22
> Yea I added some for what its worth, +1 for bumping it if it helps as its
> quite annoying.
>
> Thanks
> Szehon
>
> On Fri, Apr 3, 2015 at 2:00 PM, Lefty Leverenz <le...@gmail.com>
>
> Lefty Leverenz <ma...@gmail.com>
> April 3, 2015 at 14:00
> Thanks Szehon, if you could add some examples on INFRA-9221
> <https://issues.apache.org/jira/browse/INFRA-9221> then maybe we'd see
> some
> action.
>
> Should we bump the priority too? It seemed a small matter at first, but
> the Apache way requires complete archives and we haven't had that for
> several weeks.
>
> -- Lefty
>
>
> Szehon Ho <ma...@cloudera.com>
> April 3, 2015 at 11:51
> Hi Lefty
>
> I am also seeing this, whenever I resolve the JIRA after commit to
> trunk, I
> never get the email, and probably the contributor doesn't get the email
> either.
>
> Did you find any resolution to this (is it going to different mail list)?
> If not I can add my examples tool.
>
> Thanks
> Szehon
>
> On Fri, Mar 27, 2015 at 3:20 PM, Lefty Leverenz <le...@gmail.com>
>
> Lefty Leverenz <ma...@gmail.com>
> March 27, 2015 at 15:20
> This is still a problem. I'm working around it but the archives are
> incomplete, and that's not good.
>
> I updated INFRA-9221
> <https://issues.apache.org/jira/browse/INFRA-9221> with a few more
> examples. Can someone corroborate please (so INFRA doesn't think I'm
> a nut-case)?
>
> Thanks.
>
> -- Lefty
>
>
Re: Not getting some JIRA resolution messages
Posted by Lefty Leverenz <le...@gmail.com>.
The problem continues.
I posted a few more examples on INFRA-9221
<https://issues.apache.org/jira/browse/INFRA-9221> of issues with either
complete or incomplete messages in the issues@hive mailing list. Commits
to trunk seem to be the main problem, while branch commits usually have
complete records. But both have exceptions.
I've changed the status of INFRA-9221
<https://issues.apache.org/jira/browse/INFRA-9221> from waiting for user to
waiting for infra. Perhaps that was needed to get their attention. But I
didn't set a review date, not knowing what's appropriate.
Should I bump the priority to critical? Hive's archives are incomplete!
-- Lefty
On Fri, Apr 3, 2015 at 9:22 PM, Szehon Ho <sz...@cloudera.com> wrote:
> Yea I added some for what its worth, +1 for bumping it if it helps as its
> quite annoying.
>
> Thanks
> Szehon
>
> On Fri, Apr 3, 2015 at 2:00 PM, Lefty Leverenz <le...@gmail.com>
> wrote:
>
> > Thanks Szehon, if you could add some examples on INFRA-9221
> > <https://issues.apache.org/jira/browse/INFRA-9221> then maybe we'd see
> > some
> > action.
> >
> > Should we bump the priority too? It seemed a small matter at first, but
> > the Apache way requires complete archives and we haven't had that for
> > several weeks.
> >
> > -- Lefty
> >
> > On Fri, Apr 3, 2015 at 2:51 PM, Szehon Ho <sz...@cloudera.com> wrote:
> >
> > > Hi Lefty
> > >
> > > I am also seeing this, whenever I resolve the JIRA after commit to
> > trunk, I
> > > never get the email, and probably the contributor doesn't get the email
> > > either.
> > >
> > > Did you find any resolution to this (is it going to different mail
> list)?
> > > If not I can add my examples tool.
> > >
> > > Thanks
> > > Szehon
> > >
> > > On Fri, Mar 27, 2015 at 3:20 PM, Lefty Leverenz <
> leftyleverenz@gmail.com
> > >
> > > wrote:
> > >
> > > > This is still a problem. I'm working around it but the archives are
> > > > incomplete, and that's not good.
> > > >
> > > > I updated INFRA-9221 <
> https://issues.apache.org/jira/browse/INFRA-9221
> > >
> > > with
> > > > a few more examples. Can someone corroborate please (so INFRA
> doesn't
> > > > think I'm a nut-case)?
> > > >
> > > > Thanks.
> > > >
> > > > -- Lefty
> > > >
> > > > On Tue, Mar 3, 2015 at 4:12 AM, Lefty Leverenz <
> > leftyleverenz@gmail.com>
> > > > wrote:
> > > >
> > > >> Good call Alan, the messages are also missing from the archives so I
> > > >> filed INFRA-9221 <https://issues.apache.org/jira/browse/INFRA-9221
> >.
> > > >>
> > > >> By the way, we need to add issues@hive to the Mailing Lists
> > > >> <http://hive.apache.org/mailing_lists.html> page. I'll file a Hive
> > > JIRA
> > > >> for that.
> > > >>
> > > >> -- Lefty
> > > >>
> > > >> On Thu, Feb 26, 2015 at 6:40 PM, Alan Gates <al...@gmail.com>
> > > wrote:
> > > >>
> > > >>> The issues list should be getting all JIRA notifications except
> > CREATE,
> > > >>> you shouldn't need to watch it. You can go look at the mail
> archives
> > > to
> > > >>> see if the issue is with the list or on your end. If they aren't
> all
> > > >>> showing up in the list we should file an INFRA JIRA.
> > > >>>
> > > >>> Alan.
> > > >>>
> > > >>> Lefty Leverenz <le...@gmail.com>
> > > >>> February 26, 2015 at 14:03
> > > >>> Being a watcher could explain why I got the last two messages for
> > > >>> HIVE-9731
> > > >>> <https://issues.apache.org/jira/browse/HIVE-9731>
> > > >>> <https://issues.apache.org/jira/browse/HIVE-9731> (TODOC1.2, doc
> > > >>> comment)
> > > >>> but then why did I get all the messages before the commit, when I
> > > wasn't
> > > >>> a
> > > >>> watcher yet? And I'm not a watcher for HIVE-9509
> > > >>> <https://issues.apache.org/jira/browse/HIVE-9509>
> > > >>> <https://issues.apache.org/jira/browse/HIVE-9509> although I got
> all
> > > the
> > > >>> messages up to Ashutosh's +1.
> > > >>>
> > > >>> This is something I can work around, but if others have the same
> > > problem
> > > >>> we
> > > >>> might need to figure it out and get it fixed.
> > > >>>
> > > >>> -- Lefty
> > > >>>
> > > >>>
> > > >>> Xuefu Zhang <xz...@cloudera.com>
> > > >>> February 26, 2015 at 13:12
> > > >>> I think you get subsequent messages only if you're a watcher. You
> > > become
> > > >>> a
> > > >>> watcher after you comment or make changes for a JIRA. Is this your
> > > case?
> > > >>>
> > > >>> On Thu, Feb 26, 2015 at 1:05 PM, Lefty Leverenz
> > > >>> <le...@gmail.com> <le...@gmail.com>
> > > >>>
> > > >>> Lefty Leverenz <le...@gmail.com>
> > > >>> February 26, 2015 at 13:05
> > > >>> Is it just me, or has JIRA email been flaky since the issues
> mailing
> > > list
> > > >>> went into effect?
> > > >>>
> > > >>> For example, although I got a commit message for HIVE-9731
> > > >>> <https://issues.apache.org/jira/browse/HIVE-9731>
> > > >>> <https://issues.apache.org/jira/browse/HIVE-9731> on the
> > commits@hive
> > > >>> mailing list, I didn't get either the change of Resolution or the
> > > comment
> > > >>> about the commit -- not on dev@hive nor on issues@hive. However I
> > did
> > > >>> get
> > > >>> two subsequent messages on issues@hive when I added a TODOC1.2
> label
> > > and
> > > >>> doc comment.
> > > >>>
> > > >>> Another example: for HIVE-9509
> > > >>> <https://issues.apache.org/jira/browse/HIVE-9509>
> > > >>> <https://issues.apache.org/jira/browse/HIVE-9509> I got the commit
> > > >>> comment
> > > >>> and Fix Version change for branch-1.0.1 on the issues@hive list
> but
> > > not
> > > >>> the
> > > >>> prior commit comment and Resolved - Fix Version for 1.2.0.
> > > >>>
> > > >>> Does anyone else have this problem?
> > > >>>
> > > >>> -- Lefty
> > > >>>
> > > >>>
> > > >>
> > > >
> > >
> >
>
Re: Not getting some JIRA resolution messages
Posted by Szehon Ho <sz...@cloudera.com>.
Yea I added some for what its worth, +1 for bumping it if it helps as its
quite annoying.
Thanks
Szehon
On Fri, Apr 3, 2015 at 2:00 PM, Lefty Leverenz <le...@gmail.com>
wrote:
> Thanks Szehon, if you could add some examples on INFRA-9221
> <https://issues.apache.org/jira/browse/INFRA-9221> then maybe we'd see
> some
> action.
>
> Should we bump the priority too? It seemed a small matter at first, but
> the Apache way requires complete archives and we haven't had that for
> several weeks.
>
> -- Lefty
>
> On Fri, Apr 3, 2015 at 2:51 PM, Szehon Ho <sz...@cloudera.com> wrote:
>
> > Hi Lefty
> >
> > I am also seeing this, whenever I resolve the JIRA after commit to
> trunk, I
> > never get the email, and probably the contributor doesn't get the email
> > either.
> >
> > Did you find any resolution to this (is it going to different mail list)?
> > If not I can add my examples tool.
> >
> > Thanks
> > Szehon
> >
> > On Fri, Mar 27, 2015 at 3:20 PM, Lefty Leverenz <leftyleverenz@gmail.com
> >
> > wrote:
> >
> > > This is still a problem. I'm working around it but the archives are
> > > incomplete, and that's not good.
> > >
> > > I updated INFRA-9221 <https://issues.apache.org/jira/browse/INFRA-9221
> >
> > with
> > > a few more examples. Can someone corroborate please (so INFRA doesn't
> > > think I'm a nut-case)?
> > >
> > > Thanks.
> > >
> > > -- Lefty
> > >
> > > On Tue, Mar 3, 2015 at 4:12 AM, Lefty Leverenz <
> leftyleverenz@gmail.com>
> > > wrote:
> > >
> > >> Good call Alan, the messages are also missing from the archives so I
> > >> filed INFRA-9221 <https://issues.apache.org/jira/browse/INFRA-9221>.
> > >>
> > >> By the way, we need to add issues@hive to the Mailing Lists
> > >> <http://hive.apache.org/mailing_lists.html> page. I'll file a Hive
> > JIRA
> > >> for that.
> > >>
> > >> -- Lefty
> > >>
> > >> On Thu, Feb 26, 2015 at 6:40 PM, Alan Gates <al...@gmail.com>
> > wrote:
> > >>
> > >>> The issues list should be getting all JIRA notifications except
> CREATE,
> > >>> you shouldn't need to watch it. You can go look at the mail archives
> > to
> > >>> see if the issue is with the list or on your end. If they aren't all
> > >>> showing up in the list we should file an INFRA JIRA.
> > >>>
> > >>> Alan.
> > >>>
> > >>> Lefty Leverenz <le...@gmail.com>
> > >>> February 26, 2015 at 14:03
> > >>> Being a watcher could explain why I got the last two messages for
> > >>> HIVE-9731
> > >>> <https://issues.apache.org/jira/browse/HIVE-9731>
> > >>> <https://issues.apache.org/jira/browse/HIVE-9731> (TODOC1.2, doc
> > >>> comment)
> > >>> but then why did I get all the messages before the commit, when I
> > wasn't
> > >>> a
> > >>> watcher yet? And I'm not a watcher for HIVE-9509
> > >>> <https://issues.apache.org/jira/browse/HIVE-9509>
> > >>> <https://issues.apache.org/jira/browse/HIVE-9509> although I got all
> > the
> > >>> messages up to Ashutosh's +1.
> > >>>
> > >>> This is something I can work around, but if others have the same
> > problem
> > >>> we
> > >>> might need to figure it out and get it fixed.
> > >>>
> > >>> -- Lefty
> > >>>
> > >>>
> > >>> Xuefu Zhang <xz...@cloudera.com>
> > >>> February 26, 2015 at 13:12
> > >>> I think you get subsequent messages only if you're a watcher. You
> > become
> > >>> a
> > >>> watcher after you comment or make changes for a JIRA. Is this your
> > case?
> > >>>
> > >>> On Thu, Feb 26, 2015 at 1:05 PM, Lefty Leverenz
> > >>> <le...@gmail.com> <le...@gmail.com>
> > >>>
> > >>> Lefty Leverenz <le...@gmail.com>
> > >>> February 26, 2015 at 13:05
> > >>> Is it just me, or has JIRA email been flaky since the issues mailing
> > list
> > >>> went into effect?
> > >>>
> > >>> For example, although I got a commit message for HIVE-9731
> > >>> <https://issues.apache.org/jira/browse/HIVE-9731>
> > >>> <https://issues.apache.org/jira/browse/HIVE-9731> on the
> commits@hive
> > >>> mailing list, I didn't get either the change of Resolution or the
> > comment
> > >>> about the commit -- not on dev@hive nor on issues@hive. However I
> did
> > >>> get
> > >>> two subsequent messages on issues@hive when I added a TODOC1.2 label
> > and
> > >>> doc comment.
> > >>>
> > >>> Another example: for HIVE-9509
> > >>> <https://issues.apache.org/jira/browse/HIVE-9509>
> > >>> <https://issues.apache.org/jira/browse/HIVE-9509> I got the commit
> > >>> comment
> > >>> and Fix Version change for branch-1.0.1 on the issues@hive list but
> > not
> > >>> the
> > >>> prior commit comment and Resolved - Fix Version for 1.2.0.
> > >>>
> > >>> Does anyone else have this problem?
> > >>>
> > >>> -- Lefty
> > >>>
> > >>>
> > >>
> > >
> >
>
Re: Not getting some JIRA resolution messages
Posted by Lefty Leverenz <le...@gmail.com>.
Thanks Szehon, if you could add some examples on INFRA-9221
<https://issues.apache.org/jira/browse/INFRA-9221> then maybe we'd see some
action.
Should we bump the priority too? It seemed a small matter at first, but
the Apache way requires complete archives and we haven't had that for
several weeks.
-- Lefty
On Fri, Apr 3, 2015 at 2:51 PM, Szehon Ho <sz...@cloudera.com> wrote:
> Hi Lefty
>
> I am also seeing this, whenever I resolve the JIRA after commit to trunk, I
> never get the email, and probably the contributor doesn't get the email
> either.
>
> Did you find any resolution to this (is it going to different mail list)?
> If not I can add my examples tool.
>
> Thanks
> Szehon
>
> On Fri, Mar 27, 2015 at 3:20 PM, Lefty Leverenz <le...@gmail.com>
> wrote:
>
> > This is still a problem. I'm working around it but the archives are
> > incomplete, and that's not good.
> >
> > I updated INFRA-9221 <https://issues.apache.org/jira/browse/INFRA-9221>
> with
> > a few more examples. Can someone corroborate please (so INFRA doesn't
> > think I'm a nut-case)?
> >
> > Thanks.
> >
> > -- Lefty
> >
> > On Tue, Mar 3, 2015 at 4:12 AM, Lefty Leverenz <le...@gmail.com>
> > wrote:
> >
> >> Good call Alan, the messages are also missing from the archives so I
> >> filed INFRA-9221 <https://issues.apache.org/jira/browse/INFRA-9221>.
> >>
> >> By the way, we need to add issues@hive to the Mailing Lists
> >> <http://hive.apache.org/mailing_lists.html> page. I'll file a Hive
> JIRA
> >> for that.
> >>
> >> -- Lefty
> >>
> >> On Thu, Feb 26, 2015 at 6:40 PM, Alan Gates <al...@gmail.com>
> wrote:
> >>
> >>> The issues list should be getting all JIRA notifications except CREATE,
> >>> you shouldn't need to watch it. You can go look at the mail archives
> to
> >>> see if the issue is with the list or on your end. If they aren't all
> >>> showing up in the list we should file an INFRA JIRA.
> >>>
> >>> Alan.
> >>>
> >>> Lefty Leverenz <le...@gmail.com>
> >>> February 26, 2015 at 14:03
> >>> Being a watcher could explain why I got the last two messages for
> >>> HIVE-9731
> >>> <https://issues.apache.org/jira/browse/HIVE-9731>
> >>> <https://issues.apache.org/jira/browse/HIVE-9731> (TODOC1.2, doc
> >>> comment)
> >>> but then why did I get all the messages before the commit, when I
> wasn't
> >>> a
> >>> watcher yet? And I'm not a watcher for HIVE-9509
> >>> <https://issues.apache.org/jira/browse/HIVE-9509>
> >>> <https://issues.apache.org/jira/browse/HIVE-9509> although I got all
> the
> >>> messages up to Ashutosh's +1.
> >>>
> >>> This is something I can work around, but if others have the same
> problem
> >>> we
> >>> might need to figure it out and get it fixed.
> >>>
> >>> -- Lefty
> >>>
> >>>
> >>> Xuefu Zhang <xz...@cloudera.com>
> >>> February 26, 2015 at 13:12
> >>> I think you get subsequent messages only if you're a watcher. You
> become
> >>> a
> >>> watcher after you comment or make changes for a JIRA. Is this your
> case?
> >>>
> >>> On Thu, Feb 26, 2015 at 1:05 PM, Lefty Leverenz
> >>> <le...@gmail.com> <le...@gmail.com>
> >>>
> >>> Lefty Leverenz <le...@gmail.com>
> >>> February 26, 2015 at 13:05
> >>> Is it just me, or has JIRA email been flaky since the issues mailing
> list
> >>> went into effect?
> >>>
> >>> For example, although I got a commit message for HIVE-9731
> >>> <https://issues.apache.org/jira/browse/HIVE-9731>
> >>> <https://issues.apache.org/jira/browse/HIVE-9731> on the commits@hive
> >>> mailing list, I didn't get either the change of Resolution or the
> comment
> >>> about the commit -- not on dev@hive nor on issues@hive. However I did
> >>> get
> >>> two subsequent messages on issues@hive when I added a TODOC1.2 label
> and
> >>> doc comment.
> >>>
> >>> Another example: for HIVE-9509
> >>> <https://issues.apache.org/jira/browse/HIVE-9509>
> >>> <https://issues.apache.org/jira/browse/HIVE-9509> I got the commit
> >>> comment
> >>> and Fix Version change for branch-1.0.1 on the issues@hive list but
> not
> >>> the
> >>> prior commit comment and Resolved - Fix Version for 1.2.0.
> >>>
> >>> Does anyone else have this problem?
> >>>
> >>> -- Lefty
> >>>
> >>>
> >>
> >
>
Re: Not getting some JIRA resolution messages
Posted by Szehon Ho <sz...@cloudera.com>.
Hi Lefty
I am also seeing this, whenever I resolve the JIRA after commit to trunk, I
never get the email, and probably the contributor doesn't get the email
either.
Did you find any resolution to this (is it going to different mail list)?
If not I can add my examples tool.
Thanks
Szehon
On Fri, Mar 27, 2015 at 3:20 PM, Lefty Leverenz <le...@gmail.com>
wrote:
> This is still a problem. I'm working around it but the archives are
> incomplete, and that's not good.
>
> I updated INFRA-9221 <https://issues.apache.org/jira/browse/INFRA-9221> with
> a few more examples. Can someone corroborate please (so INFRA doesn't
> think I'm a nut-case)?
>
> Thanks.
>
> -- Lefty
>
> On Tue, Mar 3, 2015 at 4:12 AM, Lefty Leverenz <le...@gmail.com>
> wrote:
>
>> Good call Alan, the messages are also missing from the archives so I
>> filed INFRA-9221 <https://issues.apache.org/jira/browse/INFRA-9221>.
>>
>> By the way, we need to add issues@hive to the Mailing Lists
>> <http://hive.apache.org/mailing_lists.html> page. I'll file a Hive JIRA
>> for that.
>>
>> -- Lefty
>>
>> On Thu, Feb 26, 2015 at 6:40 PM, Alan Gates <al...@gmail.com> wrote:
>>
>>> The issues list should be getting all JIRA notifications except CREATE,
>>> you shouldn't need to watch it. You can go look at the mail archives to
>>> see if the issue is with the list or on your end. If they aren't all
>>> showing up in the list we should file an INFRA JIRA.
>>>
>>> Alan.
>>>
>>> Lefty Leverenz <le...@gmail.com>
>>> February 26, 2015 at 14:03
>>> Being a watcher could explain why I got the last two messages for
>>> HIVE-9731
>>> <https://issues.apache.org/jira/browse/HIVE-9731>
>>> <https://issues.apache.org/jira/browse/HIVE-9731> (TODOC1.2, doc
>>> comment)
>>> but then why did I get all the messages before the commit, when I wasn't
>>> a
>>> watcher yet? And I'm not a watcher for HIVE-9509
>>> <https://issues.apache.org/jira/browse/HIVE-9509>
>>> <https://issues.apache.org/jira/browse/HIVE-9509> although I got all the
>>> messages up to Ashutosh's +1.
>>>
>>> This is something I can work around, but if others have the same problem
>>> we
>>> might need to figure it out and get it fixed.
>>>
>>> -- Lefty
>>>
>>>
>>> Xuefu Zhang <xz...@cloudera.com>
>>> February 26, 2015 at 13:12
>>> I think you get subsequent messages only if you're a watcher. You become
>>> a
>>> watcher after you comment or make changes for a JIRA. Is this your case?
>>>
>>> On Thu, Feb 26, 2015 at 1:05 PM, Lefty Leverenz
>>> <le...@gmail.com> <le...@gmail.com>
>>>
>>> Lefty Leverenz <le...@gmail.com>
>>> February 26, 2015 at 13:05
>>> Is it just me, or has JIRA email been flaky since the issues mailing list
>>> went into effect?
>>>
>>> For example, although I got a commit message for HIVE-9731
>>> <https://issues.apache.org/jira/browse/HIVE-9731>
>>> <https://issues.apache.org/jira/browse/HIVE-9731> on the commits@hive
>>> mailing list, I didn't get either the change of Resolution or the comment
>>> about the commit -- not on dev@hive nor on issues@hive. However I did
>>> get
>>> two subsequent messages on issues@hive when I added a TODOC1.2 label and
>>> doc comment.
>>>
>>> Another example: for HIVE-9509
>>> <https://issues.apache.org/jira/browse/HIVE-9509>
>>> <https://issues.apache.org/jira/browse/HIVE-9509> I got the commit
>>> comment
>>> and Fix Version change for branch-1.0.1 on the issues@hive list but not
>>> the
>>> prior commit comment and Resolved - Fix Version for 1.2.0.
>>>
>>> Does anyone else have this problem?
>>>
>>> -- Lefty
>>>
>>>
>>
>
Re: Not getting some JIRA resolution messages
Posted by Lefty Leverenz <le...@gmail.com>.
This is still a problem. I'm working around it but the archives are
incomplete, and that's not good.
I updated INFRA-9221 <https://issues.apache.org/jira/browse/INFRA-9221> with
a few more examples. Can someone corroborate please (so INFRA doesn't
think I'm a nut-case)?
Thanks.
-- Lefty
On Tue, Mar 3, 2015 at 4:12 AM, Lefty Leverenz <le...@gmail.com>
wrote:
> Good call Alan, the messages are also missing from the archives so I filed
> INFRA-9221 <https://issues.apache.org/jira/browse/INFRA-9221>.
>
> By the way, we need to add issues@hive to the Mailing Lists
> <http://hive.apache.org/mailing_lists.html> page. I'll file a Hive JIRA
> for that.
>
> -- Lefty
>
> On Thu, Feb 26, 2015 at 6:40 PM, Alan Gates <al...@gmail.com> wrote:
>
>> The issues list should be getting all JIRA notifications except CREATE,
>> you shouldn't need to watch it. You can go look at the mail archives to
>> see if the issue is with the list or on your end. If they aren't all
>> showing up in the list we should file an INFRA JIRA.
>>
>> Alan.
>>
>> Lefty Leverenz <le...@gmail.com>
>> February 26, 2015 at 14:03
>> Being a watcher could explain why I got the last two messages for
>> HIVE-9731
>> <https://issues.apache.org/jira/browse/HIVE-9731>
>> <https://issues.apache.org/jira/browse/HIVE-9731> (TODOC1.2, doc comment)
>> but then why did I get all the messages before the commit, when I wasn't a
>> watcher yet? And I'm not a watcher for HIVE-9509
>> <https://issues.apache.org/jira/browse/HIVE-9509>
>> <https://issues.apache.org/jira/browse/HIVE-9509> although I got all the
>> messages up to Ashutosh's +1.
>>
>> This is something I can work around, but if others have the same problem
>> we
>> might need to figure it out and get it fixed.
>>
>> -- Lefty
>>
>>
>> Xuefu Zhang <xz...@cloudera.com>
>> February 26, 2015 at 13:12
>> I think you get subsequent messages only if you're a watcher. You become a
>> watcher after you comment or make changes for a JIRA. Is this your case?
>>
>> On Thu, Feb 26, 2015 at 1:05 PM, Lefty Leverenz <le...@gmail.com>
>> <le...@gmail.com>
>>
>> Lefty Leverenz <le...@gmail.com>
>> February 26, 2015 at 13:05
>> Is it just me, or has JIRA email been flaky since the issues mailing list
>> went into effect?
>>
>> For example, although I got a commit message for HIVE-9731
>> <https://issues.apache.org/jira/browse/HIVE-9731>
>> <https://issues.apache.org/jira/browse/HIVE-9731> on the commits@hive
>> mailing list, I didn't get either the change of Resolution or the comment
>> about the commit -- not on dev@hive nor on issues@hive. However I did get
>> two subsequent messages on issues@hive when I added a TODOC1.2 label and
>> doc comment.
>>
>> Another example: for HIVE-9509
>> <https://issues.apache.org/jira/browse/HIVE-9509>
>> <https://issues.apache.org/jira/browse/HIVE-9509> I got the commit
>> comment
>> and Fix Version change for branch-1.0.1 on the issues@hive list but not
>> the
>> prior commit comment and Resolved - Fix Version for 1.2.0.
>>
>> Does anyone else have this problem?
>>
>> -- Lefty
>>
>>
>
Re: Not getting some JIRA resolution messages
Posted by Lefty Leverenz <le...@gmail.com>.
Good call Alan, the messages are also missing from the archives so I filed
INFRA-9221 <https://issues.apache.org/jira/browse/INFRA-9221>.
By the way, we need to add issues@hive to the Mailing Lists
<http://hive.apache.org/mailing_lists.html> page. I'll file a Hive JIRA
for that.
-- Lefty
On Thu, Feb 26, 2015 at 6:40 PM, Alan Gates <al...@gmail.com> wrote:
> The issues list should be getting all JIRA notifications except CREATE,
> you shouldn't need to watch it. You can go look at the mail archives to
> see if the issue is with the list or on your end. If they aren't all
> showing up in the list we should file an INFRA JIRA.
>
> Alan.
>
> Lefty Leverenz <le...@gmail.com>
> February 26, 2015 at 14:03
> Being a watcher could explain why I got the last two messages for HIVE-9731
> <https://issues.apache.org/jira/browse/HIVE-9731>
> <https://issues.apache.org/jira/browse/HIVE-9731> (TODOC1.2, doc comment)
> but then why did I get all the messages before the commit, when I wasn't a
> watcher yet? And I'm not a watcher for HIVE-9509
> <https://issues.apache.org/jira/browse/HIVE-9509>
> <https://issues.apache.org/jira/browse/HIVE-9509> although I got all the
> messages up to Ashutosh's +1.
>
> This is something I can work around, but if others have the same problem we
> might need to figure it out and get it fixed.
>
> -- Lefty
>
>
> Xuefu Zhang <xz...@cloudera.com>
> February 26, 2015 at 13:12
> I think you get subsequent messages only if you're a watcher. You become a
> watcher after you comment or make changes for a JIRA. Is this your case?
>
> On Thu, Feb 26, 2015 at 1:05 PM, Lefty Leverenz <le...@gmail.com>
> <le...@gmail.com>
>
> Lefty Leverenz <le...@gmail.com>
> February 26, 2015 at 13:05
> Is it just me, or has JIRA email been flaky since the issues mailing list
> went into effect?
>
> For example, although I got a commit message for HIVE-9731
> <https://issues.apache.org/jira/browse/HIVE-9731>
> <https://issues.apache.org/jira/browse/HIVE-9731> on the commits@hive
> mailing list, I didn't get either the change of Resolution or the comment
> about the commit -- not on dev@hive nor on issues@hive. However I did get
> two subsequent messages on issues@hive when I added a TODOC1.2 label and
> doc comment.
>
> Another example: for HIVE-9509
> <https://issues.apache.org/jira/browse/HIVE-9509>
> <https://issues.apache.org/jira/browse/HIVE-9509> I got the commit comment
> and Fix Version change for branch-1.0.1 on the issues@hive list but not
> the
> prior commit comment and Resolved - Fix Version for 1.2.0.
>
> Does anyone else have this problem?
>
> -- Lefty
>
>
Re: Not getting some JIRA resolution messages
Posted by Alan Gates <al...@gmail.com>.
The issues list should be getting all JIRA notifications except CREATE,
you shouldn't need to watch it. You can go look at the mail archives to
see if the issue is with the list or on your end. If they aren't all
showing up in the list we should file an INFRA JIRA.
Alan.
> Lefty Leverenz <ma...@gmail.com>
> February 26, 2015 at 14:03
> Being a watcher could explain why I got the last two messages for
> HIVE-9731
> <https://issues.apache.org/jira/browse/HIVE-9731> (TODOC1.2, doc comment)
> but then why did I get all the messages before the commit, when I wasn't a
> watcher yet? And I'm not a watcher for HIVE-9509
> <https://issues.apache.org/jira/browse/HIVE-9509> although I got all the
> messages up to Ashutosh's +1.
>
> This is something I can work around, but if others have the same
> problem we
> might need to figure it out and get it fixed.
>
> -- Lefty
>
>
> Xuefu Zhang <ma...@cloudera.com>
> February 26, 2015 at 13:12
> I think you get subsequent messages only if you're a watcher. You become a
> watcher after you comment or make changes for a JIRA. Is this your case?
>
> On Thu, Feb 26, 2015 at 1:05 PM, Lefty Leverenz <le...@gmail.com>
>
> Lefty Leverenz <ma...@gmail.com>
> February 26, 2015 at 13:05
> Is it just me, or has JIRA email been flaky since the issues mailing list
> went into effect?
>
> For example, although I got a commit message for HIVE-9731
> <https://issues.apache.org/jira/browse/HIVE-9731> on the commits@hive
> mailing list, I didn't get either the change of Resolution or the comment
> about the commit -- not on dev@hive nor on issues@hive. However I did get
> two subsequent messages on issues@hive when I added a TODOC1.2 label and
> doc comment.
>
> Another example: for HIVE-9509
> <https://issues.apache.org/jira/browse/HIVE-9509> I got the commit comment
> and Fix Version change for branch-1.0.1 on the issues@hive list but
> not the
> prior commit comment and Resolved - Fix Version for 1.2.0.
>
> Does anyone else have this problem?
>
> -- Lefty
>
Re: Not getting some JIRA resolution messages
Posted by Lefty Leverenz <le...@gmail.com>.
Being a watcher could explain why I got the last two messages for HIVE-9731
<https://issues.apache.org/jira/browse/HIVE-9731> (TODOC1.2, doc comment)
but then why did I get all the messages before the commit, when I wasn't a
watcher yet? And I'm not a watcher for HIVE-9509
<https://issues.apache.org/jira/browse/HIVE-9509> although I got all the
messages up to Ashutosh's +1.
This is something I can work around, but if others have the same problem we
might need to figure it out and get it fixed.
-- Lefty
On Thu, Feb 26, 2015 at 1:12 PM, Xuefu Zhang <xz...@cloudera.com> wrote:
> I think you get subsequent messages only if you're a watcher. You become a
> watcher after you comment or make changes for a JIRA. Is this your case?
>
> On Thu, Feb 26, 2015 at 1:05 PM, Lefty Leverenz <le...@gmail.com>
> wrote:
>
> > Is it just me, or has JIRA email been flaky since the issues mailing list
> > went into effect?
> >
> > For example, although I got a commit message for HIVE-9731
> > <https://issues.apache.org/jira/browse/HIVE-9731> on the commits@hive
> > mailing list, I didn't get either the change of Resolution or the comment
> > about the commit -- not on dev@hive nor on issues@hive. However I did
> get
> > two subsequent messages on issues@hive when I added a TODOC1.2 label and
> > doc comment.
> >
> > Another example: for HIVE-9509
> > <https://issues.apache.org/jira/browse/HIVE-9509> I got the commit
> comment
> > and Fix Version change for branch-1.0.1 on the issues@hive list but not
> > the
> > prior commit comment and Resolved - Fix Version for 1.2.0.
> >
> > Does anyone else have this problem?
> >
> > -- Lefty
> >
>
Re: Not getting some JIRA resolution messages
Posted by Xuefu Zhang <xz...@cloudera.com>.
I think you get subsequent messages only if you're a watcher. You become a
watcher after you comment or make changes for a JIRA. Is this your case?
On Thu, Feb 26, 2015 at 1:05 PM, Lefty Leverenz <le...@gmail.com>
wrote:
> Is it just me, or has JIRA email been flaky since the issues mailing list
> went into effect?
>
> For example, although I got a commit message for HIVE-9731
> <https://issues.apache.org/jira/browse/HIVE-9731> on the commits@hive
> mailing list, I didn't get either the change of Resolution or the comment
> about the commit -- not on dev@hive nor on issues@hive. However I did get
> two subsequent messages on issues@hive when I added a TODOC1.2 label and
> doc comment.
>
> Another example: for HIVE-9509
> <https://issues.apache.org/jira/browse/HIVE-9509> I got the commit comment
> and Fix Version change for branch-1.0.1 on the issues@hive list but not
> the
> prior commit comment and Resolved - Fix Version for 1.2.0.
>
> Does anyone else have this problem?
>
> -- Lefty
>